Antigravity IDE freezes/unresponsive when opening any folder (Linux, Nvidia)

Google Antigravity
,
1

Antigravity IDE — UI freezes/unresponsive on startup when opening any folder (Linux, Nvidia)

Summary

Antigravity IDE consistently becomes unresponsive (~15-20s after window opens) when opening any folder, including an empty one, even with --disable-extensions. The freeze repeats indefinitely with “CodeWindow: detected unresponsive” errors every ~15-20 seconds. Fully reproducible on a clean install/profile.

Environment

  • OS: Parrot OS (Debian-based), kernel Linux
  • Desktop session: Wayland (XDG_SESSION_TYPE=wayland)
  • GPU: NVIDIA GeForce GTX 1060, Driver 550.163.01, CUDA 12.4
  • Antigravity version: 1.107.0 (commit 15487b3041e65228cae24980a3f796c905ef582c), x64
  • Install method: official APT repo (us-central1-apt.pkg.dev, antigravity-debian)

Steps to reproduce

  1. Fresh install / full reset of ~/.config/Antigravity
  2. Set fs.inotify.max_user_watches=524288 (ruled out inotify limits as the cause)
  3. Open a nearly-empty folder (1 file, 1 subfolder — .vscode):
antigravity --disable-extensions ~/qualquer-pasta
  1. Window opens, becomes unresponsive within ~15-20 seconds
  2. Repeats every ~15-20s with CodeWindow: detected unresponsive in main.log

Ruled out

  • Not folder size/file count: reproduces on a folder with 1 file
  • Not extensions: reproduces with --disable-extensions
  • Not GPU rendering: reproduces with --disable-gpu
  • Not inotify watch limits: increased to 524288, no change
  • Not stale cache: reproduces after full ~/.config/Antigravity wipe

Key log evidence (main.log)

Repeated UnresponsiveSampleError with this call stack pattern:

at PJr (.../workbench.desktop.main.js:3270:49337)
at Array.sort (<anonymous>)
at Z_t (.../workbench.desktop.main.js:3270:39240)
...
at o2n.setSelectedModel (.../workbench.desktop.main.js:5143:75156)
at o2n.Kb (.../workbench.desktop.main.js:5143:84636)

This suggests the main thread blocks while sorting/selecting the AI model list (setSelectedModel) during window initialization — likely a synchronous call related to model listing/selection happening on the UI thread.

Full main.log (reproducible freeze on empty folder + --disable-extensions)

2026-07-22 22:52:59.288 [info] [BrowserOnboardingClientMainService] Starting browser onboardingserver
2026-07-22 22:52:59.295 [info] [BrowserOnboardingClientServer] Browser onboarding server started on http://localhost:43991
2026-07-22 22:52:59.363 [info] update#setState idle
2026-07-22 22:53:17.100 [error] CodeWindow: detected unresponsive
2026-07-22 22:53:29.364 [info] update#setState checking for updates
2026-07-22 22:53:30.010 [info] update#setState available for download
2026-07-22 22:53:32.102 [error] [uncaught exception in main]: UnresponsiveSampleError: from window with ID 1 belonging to process with pid 25862
at PJr (workbench.desktop.main.js:3270:49337)
at Array.sort (<anonymous>)
at Z_t (workbench.desktop.main.js:3270:39240)
...
at o2n.setSelectedModel (workbench.desktop.main.js:5143:75156)
at o2n.Kb (workbench.desktop.main.js:5143:84636)
...
Total Samples: 14
2026-07-22 22:53:56.614 [error] CodeWindow: detected unresponsive
2026-07-22 22:54:11.614 [error] [uncaught exception in main]: UnresponsiveSampleError: from window with ID 1 belonging to process with pid 25862
at PJr (workbench.desktop.main.js:3270:49337)
at Array.sort (<anonymous>)
at Z_t (workbench.desktop.main.js:3270:39240)
...
Total Samples: 14
For full overview of the unresponsive period, capture cpu profile via https://aka.ms/vscode-tracing-cpu-profile

Additional info

Happy to provide the full nvidia-smi output or test further configurations if helpful.