It’s hard to believe that at least two days have passed and no patch to fix this.
Let’s get this sorted team!
Thank you very much!
This worked, thanks!
Wonderful! Worked here. In my opinion a oficial fix should be available at this point (Google Team)
Me too. I am experiencing this identical regression on Windows 10 after a fresh reload today. The application initializes directly to a persistent, completely black screen.
The recommended fixes in this thread involving dropping the Electron sandbox safety layers (--no-sandbox) or completely purging the %APPDATA%\Antigravity cache folders are not sustainable production solutions for professional workspaces. Deleting those cache structures strips out active conversational context history, local token configurations, and agent state maps.
The logging confirms a file-lock conflict: language_server.exe stalls out as a zombie background thread on exit and continues holding an active database handle lock on the local storage partition. When a new instance attempts initialization, the storage bridge crashes silently before the primary UI layer can ever be composited.
Please release an official, clean hotfix (v2.0.7+) that explicitly hard-terminates rogue backend server processes on exit and resolves this initialization deadlock natively.
Environment Details:
- OS Version: Windows 10 x64 (Build 19045)
- App Revision: v2.0.6 Official Build
- Hardware: Standalone Developer Workstation
Hi @Dannyy,
This issue has been resolved in Antigravity 2.0.11. Try updating to the latest version and let us know if you run into any other issues.
Thank you very much, this works for me, wow that was a big one 