Antigravity 2.0 White Screen Issue Resolution Share

Google Antigravity
1

Antigravity 2.0 White Screen Issue Resolution Share

Sharing this to help anyone troubleshooting the “White Screen” (blank UI) issue on Antigravity v2.0.6 (Electron-based app). If you are experiencing a complete freeze or a blank white window right after launching, this guide is for you.

1. Root Cause Analysis

According to the CLI/CMD logs, the core issue stems from the internal Chromium engine failing to initialize the rendering pipeline with certain GPU driver environments, throwing ContextResult::kFatalFailure: Failed to create shared context for virtualization. On the Windows OS level, it triggers a fatal DirectX initialization failure with exit_code=-2147483645 (0x80004005), causing the UI rendering loop to completely collapse before drawing the interface.

2. Why Standard Fixes Failed (What blocked it)

Standard fallback flags like --disable-gpu or --disable-software-rasterizer alone did not solve the issue. This is due to Chromium’s internal security sandbox restrictions. Once the GPU initialization crashed, the sandbox actively blocked the CPU from executing software rasterization routines on the system kernel level. Furthermore, Windows hardware acceleration features (such as HAGS) forced priority conflicts over window rendering controls, leading to instant app termination.

3. Troubleshooting Attempted

  • Full application uninstallation and reinstallation (Failed)

  • Complete purging of AppData\Local and AppData\Roaming\Antigravity cache directories (Temporary fix, but regressed upon turning on hardware acceleration)

  • Toggling Windows Hardware-Accelerated GPU Scheduling (HAGS) and restarting PC (Failed)

  • Running native flags via CMD: --disable-gpu, --disable-gpu-compositing, --use-gl=swiftshader (White screen persisted)

4. The Final Working Solution

The issue was successfully bypassed by forcing a specific combination of advanced runtime flags that completely tear down the sandbox barriers and priority locks, forcing the app to drop back to stable CPU software rendering.

  • The Working Command Line:

Plaintext

Antigravity.exe --disable-gpu --disable-gpu-sandbox --no-sandbox --disable-features=GpuProcessHighPriorityPerWindow

[How it works]

  • --no-sandbox & --disable-gpu-sandbox: Completely tears down the internal engine container barriers, allowing the CPU to directly fetch system resources to force-draw the UI layout.

  • --disable-features=GpuProcessHighPriorityPerWindow: Disables the buggy priority feature that causes the Windows Desktop Window Manager (DWM) and the Electron engine to fight over GPU rendering dominance.

If your app is currently frozen on a white screen, right-click your Antigravity Shortcut ➔ Properties ➔ Shortcut Tab, and append the above flags to the end of the Target field. Hopefully, the dev team will implement proper exception handling for GPU context allocation in the upcoming patches.

2

Amazing! It works. But at the same time I just can’t believe how google can be so sloppy. I am a paying ultra user and I have to deal with stuff like that? get your grips!