# Close Antigravity trigger a coredump on Linux **URL:** \ **Category:** Google Antigravity\ **Tags:** bug\ **Created:** [February 25, 2026, 1:25pm UTC](https://discuss.ai.google.dev/t/close-antigravity-trigger-a-coredump-on-linux/126682 "2026-02-25T13:25:53Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![postadelmaga](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/postadelmaga/32/98087_2.png) [@postadelmaga](https://discuss.ai.google.dev/u/postadelmaga)\ **Post date:** [February 25, 2026, 1:25pm UTC](https://discuss.ai.google.dev/t/close-antigravity-trigger-a-coredump-on-linux/126682/1 "2026-02-25T13:25:53Z")
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` ` ` ---
**Author:** ![altuhovsu](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/altuhovsu/32/116302_2.png) [@altuhovsu](https://discuss.ai.google.dev/u/altuhovsu)\ **Post date:** [April 18, 2026, 10:47am UTC](https://discuss.ai.google.dev/t/close-antigravity-trigger-a-coredump-on-linux/126682/2 "2026-04-18T10:47:44Z")
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 ?? () ---
**Author:** ![Ramon\_Suarez](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/ramon_suarez/32/119789_2.png) [@Ramon\_Suarez](https://discuss.ai.google.dev/u/Ramon_Suarez)\ **Post date:** [May 4, 2026, 6:57pm UTC](https://discuss.ai.google.dev/t/close-antigravity-trigger-a-coredump-on-linux/126682/3 "2026-05-04T18:57:42Z")
**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. ---
**Author:** ![s-6d](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/s-6d/32/102369_2.png) [@s-6d](https://discuss.ai.google.dev/u/s-6d)\ **Post date:** [May 5, 2026, 12:01pm UTC](https://discuss.ai.google.dev/t/close-antigravity-trigger-a-coredump-on-linux/126682/4 "2026-05-05T12:01:18Z")
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. ---
**Author:** ![Anupam96786](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/anupam96786/32/102971_2.png) [@Anupam96786](https://discuss.ai.google.dev/u/Anupam96786)\ **Post date:** [May 18, 2026, 4:57pm UTC](https://discuss.ai.google.dev/t/close-antigravity-trigger-a-coredump-on-linux/126682/5 "2026-05-18T16:57:46Z")
> [@Ramon\_Suarez](#): > > 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. 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: ```ini [Coredump] Storage=none ProcessSizeMax=0 ``` After saving the file, make sure to reload the systemd daemon to apply the changes: ```bash 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. ---
**Author:** ![DesertWayfarer](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/desertwayfarer/32/139249_2.png) [@DesertWayfarer](https://discuss.ai.google.dev/u/DesertWayfarer)\ **Post date:** [July 27, 2026, 3:45pm UTC](https://discuss.ai.google.dev/t/close-antigravity-trigger-a-coredump-on-linux/126682/6 "2026-07-27T15:45:50Z")
perfect solution for this strange problem, thank you 🙂