Antigravity Desktop App Crashes on Startup Due to GPU Process Failure

Google Antigravity
1

Summary

The Antigravity desktop application fails to start on Windows 11. The application backend initializes successfully, but the Electron/Chromium frontend repeatedly crashes because the GPU process cannot be initialized.

Environment

  • Antigravity Version: 2.1.4

  • OS: Windows 11

  • CPU: Intel Core i3-1215U (12th Gen)

  • GPU: Intel UHD Graphics

  • Graphics Driver Version: 31.0.101.4255

  • Architecture: x64

Steps to Reproduce

  1. Install Antigravity 2.1.4 from the official Google download page.

  2. Launch Antigravity from the Start Menu or installation directory.

  3. Observe a brief black screen.

  4. Application exits automatically.

Expected Behavior

Antigravity should launch and display the main application window.

Actual Behavior

The application briefly opens, displays a black window (or flashes a black screen), and then exits.

Relevant Logs

Electron output:

GPU process exited unexpectedly: exit_code=-2147483645
GPU process exited unexpectedly: exit_code=-2147483645
GPU process exited unexpectedly: exit_code=-2147483645
FATAL: GPU process isn't usable. Goodbye.

Application log:

[IDE Wizard] Already shown, skipping.
Starting app (v2.1.4) with dynamic port...

Spawning:
...language_server.exe ...

[Auto-Restart] Port changed! Reloading all windows with URL:
https://127.0.0.1:<dynamic-port>/

Language server log:

Language server listening on random port for HTTPS (gRPC)
Language server listening on random port for HTTP

Additional Findings

  • Installation completes successfully.

  • The language server starts successfully.

  • Local HTTPS endpoints are created successfully.

  • Multiple launches reproduce the issue consistently.

  • The backend appears healthy.

  • Failure occurs in the Electron/Chromium rendering layer during GPU initialization.

Workarounds Attempted

  • Reinstallation

  • Running as Administrator

  • Launching with --disable-gpu

  • Launching with additional Chromium GPU-disabling flags

Result:

  • GPU-related crash behavior changes, but the desktop application remains unusable.

Assessment

This appears to be an Electron/Chromium GPU initialization failure rather than a backend or installation issue. The application services start correctly, but the frontend exits after repeated GPU process failures.

1 Like