Close Antigravity trigger a coredump on Linux

Google Antigravity
1

Closing Antigravity cause a coredump on electron39

I’am not sure if this is related to the issue but every time I start antigravity I see:
Warning: 'app' is not in the list of known options, but still passed to Electron/Chromium.

The crash occurs in the NodeService utility process during shutdown. It’s a SIGSEGV at address 0x7fcccb974775. Occurs on CachyOS using Electron 39.

❯ coredumpctl debug electron --debugger-arguments="--batch -ex 'bt'" > crash_report.txt

cat crash_report.txt
PID: 6255 (electron)
UID: 1000 (fra)
GID: 1000 (fra)
Signal: 11 (SEGV)
Timestamp: Wed 2026-02-25 14:04:00 CET (6min ago)
Command Line: /proc/self/exe --type=utility --utility-sub-type=node.mojom.NodeService --lang=it --service-sandbox-type=none --no-sandbox --render-node-override=/dev/dri/renderD128 --cras
hpad-handler-pid=6165 --enable-crash-reporter=b0fe3418-acac-440f-90be-a53d3c8d0a67,no_channel --user-data-dir=/home/fra/.config/Antigravity --standard-schemes=vscode-webview,vscode-file --
secure-schemes=vscode-webview,vscode-file --cors-schemes=vscode-webview,vscode-file --fetch-schemes=vscode-webview,vscode-file --service-worker-schemes=vscode-webview --code-cache-schemes=
vscode-webview,vscode-file --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,268489407850916024,13719731171635359285,262144 --enable-features=DocumentPolicyIncludeJSCall
StacksInCrashReports,EarlyEstablishGpuChannel,EstablishGpuChannelAsync,PdfUseShowSaveFilePicker --disable-features=CalculateNativeWinOcclusion,LocalNetworkAccessChecks,ScreenAIOCREnabled,S
pareRendererForSitePerProcess,TraceSiteInstanceGetProcessCreation --variations-seed-version --trace-process-track-uuid=3190708992871164437
Executable: /usr/lib/electron39/electron
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.chromium.Chromium-6141.scope
Unit: user@1000.service
User Unit: app-org.chromium.Chromium-6141.scope
Slice: user-1000.slice
Owner UID: 1000 (fra)
Boot ID: d50ac91c201c41bc8ac66d2d8dcf16fe
Machine ID: 32759daa90c14cfab899f7f81e9a3597
Hostname: fra-cachyos-x8664
Storage: /var/lib/systemd/coredump/core.electron.1000.d50ac91c201c41bc8ac66d2d8dcf16fe.6255.1772024640000000.zst (truncated)
Size on Disk: 7.8M
Message: Process 6255 (electron) of user 1000 dumped core.

Stack trace of thread 6255:
#0 0x00007fcccb974775 n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64

2

Same issue on Kubuntu 26.04
antigravity crashed with SIGSEGV
antigravity 1.23.2-1776332190 [origin: antigravity-debian]
/proc/self/exe --type=utility --utility-sub-type=node.mojom.NodeService --lang=en-GB --service-sandbox-type=none --render-node-override=/dev/dri/renderD128 --crashpad-handler-pid=2421 --enable-crash-reporter=8fc0cd1c-4e80-4c50-8598-58926c8c99db,no_channel --user-data-dir=/home/dmitriy/.config/Antigravity --standard-schemes=vscode-webview,vscode-file --enable-sandbox --secure-schemes=vscode-webview,vscode-file --cors-schemes=vscode-webview,vscode-file --fetch-schemes=vscode-webview,vscode-file --service-worker-schemes=vscode-webview --code-cache-schemes=vscode-webview,vscode-file --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,2781213137480100989,594780459707126307,262144 --enable-features=DocumentPolicyIncludeJSCallStacksInCrashReports,EarlyEstablishGpuChannel,EstablishGpuChannelAsync,PdfUseShowSaveFilePicker --disable-features=CalculateNativeWinOcclusion,LocalNetworkAccessChecks,ScreenAIOCREnabled,SpareRendererForSitePerProcess,TraceSiteInstanceGetProcessCreation --variations-seed-version --trace-process-track-uuid=3190709004115666625

#0 0x00007abfc14a6775 in ?? ()

3

Crash while Antigravity is running (not only on close) – huge coredump on Linux

  • Antigravity version: 1.107.0

  • Distribution: Manjaro Linux 26.0.4

  • Desktop: GNOME + Wayland

  • RAM: 32 GB

Problem:
When Antigravity is open and in use (especially during indexing / AI operations / opening large projects), it crashes with SIGSEGV / SIGABRT / etc.
The systemd-coredump then tries to write a full ~8 GB core dump, temporarily filling my root partition (only 28 GB free) and causing “disk full” warnings + system freeze for minutes.

4

I tested on both Gnome and KDE, using both RPM and DEB packages, on openSUSE and Aurora (Fedora-based distros).
I have had this issue since at least version 1.19. It is very annoying, and I already contacted support a long time ago through at least three channels.

I don’t think it will be resolved anytime soon, but at least the IDE is still working.

If you’re new to Antigravity, back in version 1.19 we also have a very handy feature: you could make small edits with Ctrl + I. However, it is currently broken on Linux and macOS, as far as I know.

5

I ran into this exact same issue. You can prevent the system freeze by disabling the core dump storage while still retaining the crash logs in the journal.

Open your /etc/systemd/coredump.conf file and add or update the following lines:

[Coredump]
Storage=none
ProcessSizeMax=0

After saving the file, make sure to reload the systemd daemon to apply the changes:

sudo systemctl daemon-reload

This tells systemd-coredump to stop writing those massive dump files to your disk, completely avoiding the “disk full” warnings and system freezes, but it will still properly record the crash event itself.

6

perfect solution for this strange problem, thank you :slight_smile: