Antigravity repeatedly crashes on Ubuntu 24.04 due to OOM killer and GPU process failure (Electron + NVIDIA)

Google Antigravity
,
1

Environment

  • OS: Ubuntu 24.04 LTS (Noble)

  • RAM: 16 GB (2×8 GB DDR5 4800 MHz)

  • Swap: 4 GB

  • GPU: NVIDIA (proprietary driver)

  • Desktop: GNOME (Wayland/Xorg)

  • Antigravity version: 1.14.2-1768287740 (installed via apt)

  • Install type: native Linux app (Electron-based)

Description

Antigravity crashes frequently on Linux due to the system OOM killer, despite sufficient available RAM (6–8 GB free at crash time).

The crash is always preceded by:

  • Extremely large virtual memory reservations by Antigravity processes (VSZ ~1.4 TB)

  • GPU-related errors from Chromium/Electron

  • NVIDIA driver reporting GPU out-of-memory

  • systemd / kernel killing the Antigravity process

This makes the application unusable for more than a few minutes.

Observed behavior

  • Antigravity launches normally

  • After several minutes of use (editing, AI interactions, background profiling):

    • GPU process crashes

    • Renderer and extension hosts fail

    • system OOM killer terminates Antigravity

  • App closes completely

Expected behavior

Antigravity should not be OOM-killed on a system with 16 GB RAM and low overall memory pressure.

Relevant Logs

Kernel OOM kill:

Out of memory: Killed process (antigravity)
total-vm: ~1480000000 kB
anon-rss: ~300MB–1GB
oom_score_adj: 300

NVIDIA driver error:

NVRM: nvCheckOkFailedNoLog: Out of memory [NV_ERR_NO_MEMORY]

Electron / Chromium GPU errors:

GPU process isn't usable. Goodbye.
GPU process launch failed: error_code=1002

systemd:

app-gnome-antigravity.scope: Failed with result 'oom-kill'

Additional Observations

  • Multiple Antigravity processes reserve ~1.4 TB of virtual memory (VSZ), which appears abnormal

  • The issue is reproducible

  • System memory is not actually exhausted at crash time

2

Hi @Frataque ,

Thank you for flagging this issue. We recommend updating to the latest version of Antigravity and checking whether the issue still occurs. Please let us know if the problem persists after updating.

1 Like