Hi Antigravity Development Team,
I am reporting a critical startup crash with the Antigravity 2.0 IDE on Windows. When I launch the application, it loads for about 2 seconds and then silently terminates without showing any UI or error popups. Reinstalling the 2.0 did not fix the issue.
I ran some diagnostics with ELECTRON_ENABLE_LOGGING=1 and found that the underlying Chromium sandbox is violently rejecting the GPU process initialization.
Crash Details:
-
The Electron sandbox throws this error instantly on launch:
[ERROR:content\browser\gpu\gpu_process_host.cc:999] GPU process exited unexpectedly: exit_code=-2147483645 -
It attempts to restart the GPU process 9 times in a fraction of a second.
-
It finally hits a fatal breakpoint and terminates:
[FATAL:content\browser\gpu\gpu_data_manager_impl_private.cc:415] GPU process isn't usable. Goodbye.
System Environment:
-
OS: Windows
-
GPU: NVIDIA (Latest Drivers)
-
Antivirus: Windows Defender Only
-
Exploit Protection: Default (
NOTSETacross the board, no forced CFG) -
Overlays: None (No Discord, MSI Afterburner, etc.)
Workarounds Tested:
-
Launching with
--disable-gpu,--disable-software-rasterizer, and--disable-gpu-compositingfailed (the sandbox still hit the exact sameSTATUS_BREAKPOINTand crashed). -
Launching the shortcut with
--no-sandboxsuccessfully bypasses the crash and allows the to run perfectly.
Because this is a STATUS_BREAKPOINT (-2147483645) error that ignores standard GPU-disabling flags, it appears to be a deep OS-level Sandbox conflict in the version of Electron currently bundled with Antigravity 2.0. (I experienced the exact same sandbox crash with another Electron app, Wispr Flow, on the same machine).
I am currently using --no-sandbox as a temporary workaround to get my work done, but could you please investigate updating the Electron framework or pushing a patch to resolve this sandbox incompatibility?
Thank you!