Antigravity IDE dumps core on exit/close | node.mojom.NodeService Signal 5 (TRAP)

Google Antigravity
,
1

Hi everyone,

I’m posting a persistent core dump issue with Antigravity IDE on Kubuntu 26.04 .

Important Context: The IDE actually runs perfectly fine and does not crash during active use. However, the exact moment I close/exit the application, it triggers a crash massage.

It seems like the parent process might be forcefully terminating the Node utility service during the cleanup routine rather than letting it shut down gracefully.

Here are my environment details and the systemd log output from the exit crash:

  • OS: Kubuntu 26.04 LTS

  • Hardware: HP Pavilion Gaming Laptop

  • IDE: Antigravity IDE (installed in /opt/)

Crash Log / Core Dump Output:

Hi everyone,

I’m posting a persistent core dump issue with Antigravity IDE on Linux.

Important Context: The IDE actually runs perfectly fine and does not crash during active use. However, the exact moment I close/exit the application, it triggers a Signal: 5 (TRAP) core dump from the internal utility process (node.mojom.NodeService).

It seems like the parent process might be forcefully terminating the Node utility service during the cleanup routine rather than letting it shut down gracefully.

Here are my environment details and the systemd log output from the exit crash:

  • OS: Linux (X86-64)

  • Hardware: HP Pavilion

  • IDE: Antigravity IDE (installed in /opt/)

Crash Log / Core Dump Output:

Plaintext

           PID: 56288 (antigravity-ide)
           UID: 1000 (satyam)
           GID: 1000 (satyam)
        Signal: 5 (TRAP)
     Timestamp: Sun 2026-05-24 12:53:18 IST
  Command Line: /proc/self/exe --type=utility --utility-sub-type=node.mojom.NodeService --lang=en-US --service-sandbox-type=none --render-node-override=/dev/dri/renderD129 --enable-crash-reporter=2dff99a4-b2dc-4d51-96d5-3e9fff745b41,no_channel $'--user-data-dir=/home/satyam/.config/Antigravity IDE' --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,7480192477036278307,6641189116883132780,262144 --enable-features=DocumentPolicyIncludeJSCallStacksInCrashReports,EarlyEstablishGpuChannel,EstablishGpuChannelAsync,PdfUseShowSaveFilePicker --disable-features=CalculateNativeWinOcclusion,LocalNetworkAccessChecks,ScreenAIOCREnabled,SpareRendererForSitePerProcess,TraceSiteInstanceGetProcessCreation --variations-seed-version --trace-process-track-uuid=3190708997556373...
    Executable: /opt/Antigravity IDE/antigravity-ide
       Storage: /var/lib/systemd/coredump/core.antigravity-ide.1000...zst (truncated)
  Size on Disk: 5.6M
       Message: Process 56288 (antigravity-ide) of user 1000 dumped core.
                
                Stack trace of thread 56288:
                #0  0x00006088f8a63e23 n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64

While it isn’t breaking my workflow since it only happens on exit, leaving dead core dumps behind isn’t ideal. Has anyone else noticed this behavior upon closing the IDE, or is there an internal shutdown flag I can tweak?

Thanks!

1 Like