Description
The unpacked root directory inside the official Linux .tar.gz distribution for the Antigravity IDE contains a literal space character (Antigravity IDE/).
When executing the application binary on modern Linux environments, the underlying Chromium/Electron framework’s internal process manager breaks at runtime. Specifically, LaunchProcess fails to safely escape or quote the execution path arguments when attempting to initialize the unprivileged user namespace/Zygote sandbox infrastructure.
Because the path string truncates prematurely at the space character, the application fails to resolve the helper binaries, throws an Invalid argument (22) trace/breakpoint trap, and immediately core dumps.
Steps to Reproduce
Download and extract the official Linux release tarball: tar -xvf antigravity-ide-linux.tar.gz
Notice the generated root folder layout is “Antigravity IDE/” with a space.
Move into the directory and attempt to execute the binary: ./antigravity-ide
Observe the immediate initialization failure and subsequent application core dump:
FATAL:zygote_host_impl_linux.cc] Check failed. : Invalid argument (22)
Expected Behaviour
The root folder inside the compressed distribution tarball should follow standard Linux packaging conventions and utilize a hyphen or underscore (e.g., Antigravity-IDE/).
Suggested Fix for the Release Pipeline
In the CI/CD packaging/distribution workflow scripts, please update the target archive directory mapping definition from:
tar -czf antigravity-ide-linux.tar.gz “Antigravity IDE/”
To a standardized, hyphenated directory name:
tar -czf antigravity-ide-linux.tar.gz “Antigravity-IDE/”
This trivial adjustment to the archival routines will completely eliminate path-chopping initialization bugs and provide seamless out-of-the-box execution for Linux desktop environments.
Downloaded a fresh tgz for Antigravity IDE
Unpacked it, left the folder with a space, and set the chrome-sandbox privs correctly
Started Antigravity IDE, and it immediately faulted
PID: 1161480 (antigravity-ide)
UID: 1000 )
GID: 1000 (willm)
Signal: 11 (SEGV)
Timestamp: Fri 2026-09-04 08:54:13 MDT (8s ago)
Command Line: /proc/self/exe --type=utility --utility-sub-type=node.mojom.NodeService --lang=en-US --service-sandbox-type=none --crashpad-handler-pid=1160349 --enable-crash-reporter=7d107534-6bf6-4abb-b248-bb665ec71c31,no_channel $'--user-data-dir=/home/willm/.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,8388480381043935157,9456153331336327779,262144 --enable-features=DocumentPolicyIncludeJSCallStacksInCrashReports,EarlyEstablishGpuChannel,EstablishGpuChannelAsync,PdfUseShowSaveFilePicker --disable-features=CalculateNativeWinOcclusion,LocalNetworkAccessChecks,ScreenAIOCREnabled,SpareRendererForSitePerProcess,TraceSiteInstanceGetProcessCreation --variations-seed-version --trace-process-track-uuid=3190709003178624776
Executable: /home/willm/Antigravity IDE/antigravity-ide
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.chromium.Chromium-1160328.scope
Unit: user@1000.service
User Unit: app-org.chromium.Chromium-1160328.scope
Slice: user-1000.slice
Owner UID: 1000 (willm)
Boot ID: 9fab8f8337be4f3c8551813706a2f..
Machine ID: 7c2c6844d22545e58747921cc8f2...
Hostname: prot..
Storage: /var/lib/systemd/coredump/core.antigravity-ide.1000.9fab8f8337be4f3c8551813706a2f0c6.1161480.1788533653000000.zst (present)
Size on Disk: 5.1M
Message: Process 1161480 (antigravity-ide) of user 1000 dumped core.
Stack trace of thread 1161480:
#0 0x000074deb7953775 n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64
Renamed the folder to Antigravity-IDE, and no faults.
I can still duplicate it, and I can still fix it with a simple fix.
I can also see the space in the folder name in the tgz; anyone should be able to see the problem.