Summary
Since auto-updating from 2.28.2 to 2.29.0, the desktop app’s language server crashes repeatedly with exited with code 2. The window flashes black and reloads (“Port changed! Reloading all windows”), and after 3 crashes in a row it gives up (“Language server crashed 3 times in a row. Giving up”). Downgrading to 2.28.2 with the same data and the same usage pattern restores stability.
Environment
- Antigravity desktop app 2.29.0 (Language server version 2.29.0), Windows x64
- Windows: Microsoft Windows 11 Pro build 26200, RAM: 64 GB
- Usage: several long-running agent processes; I follow them from my phone via Remote Control
Crash frequency by version (counted from main.log on the same machine)
| Version | Language server crashes | “Giving up” events | Period |
|---|---|---|---|
| 2.28.2 | 2 | 0 | ~6 days continuously open |
| 2.29.0 | 33 | 4 | < 1 day (some during my own testing) |
Crash signatures (language_server.log)
All variants point to the same code path: the protobuf decoder (google_arena_unsafe) receives a type pointer where an allocation size is expected.
Variant A — bogus out of memory
runtime: out of memory: cannot allocate 140700171632640-byte block (2110783488 in use)
fatal error: out of memory
goroutine 533 [running]:
runtime.mallocgc(0x7ff74f80eb78, 0x7ff74f80eb78, 0x0)
.../protobuf/v2/internal/impl/impl.newObject (google_arena_unsafe.go:174)
.../protobuf/v2/internal/impl/impl.consumeMessageInfo (codec_field.go:200)
.../protobuf/v2/internal/impl/impl.(*MessageInfo).unmarshalPointerEager
The requested size (0x7FF74F80EB78) is an address inside the executable image, not a size. The same value shows up in rbx in the register dump of Variant B.
Variant B — execution at address 0
Exception 0xc0000005 0x8 0x0 0x0
PC=0x0
runtime: g 474: unknown pc 0x270e
The goroutine is the summaries reconciler (reconcile_summaries.go), which crashes right after logging [Summaries] failed to generate summary for <id> while reconciling: conversation <id> not found.
Variant C — wild PC / corrupted return address
Exception 0xc0000005 0x8 0x16c456609e0 0x16c456609e0
PC=0x16c456609e0
runtime: g 16587: unknown pc 0x16c456609e0 (created by actor/tracing.Go)
runtime: g 319: unexpected return pc for runtime.mallocgc called from 0x195
In this case mallocgc again receives a type pointer as the size, and returns into the protobuf impl region.
Trigger correlation
- With a Remote Control session (phone): the session opened at 09:30:27 (
mesh_routing.go: Pinned server-vouched WebCrypto public key for session ...), and the crash followed at 09:31:34. Before any mitigation, crashes came about 1 minute after the phone connected. - Without the phone: about 4 minutes until a crash with the original data. After compacting the conversation databases, about 52 minutes (still crashes, with no remote session, while the agent is actively working).
- Conversation size matters: several conversation DBs in
~/.gemini/antigravity/conversations/were 0.9–1.3 GB each. The largest active one had 80,006 steps (~460 MB of real data).Checkpoint summary was too long and was truncated to 38400 tokensappears for it. At the time of Variant A, the Go heap was at 2.1 GB. - Moving the largest conversations and
conversation_summaries.db/agyhub_summaries_proto.pbout only delays the crash, because the summaries are regenerated from the remaining conversations and the crash comes back.
Ruled out
- GPU: still crashes with hardware acceleration disabled. No Crashpad dumps; it is the Go process exiting, not Electron.
- Hardware: no relevant WHEA events, and no other common apps crashing.
- A single “poisoned” conversation: the crash moves between subsystems (summaries, tracing, allocation), which is consistent with an unsafe-arena decoding bug under large payloads rather than with one bad record.
Workaround that works
- Back up
~/.gemini/antigravityand%APPDATA%\Antigravity(do not delete them). - Install 2.28.2 over 2.29.0.
winget download --id Google.Antigravity --version 2.28.2gets the official, Google-signed installer from storage.googleapis.com. - Prevent the auto-updater from reinstalling 2.29.0. It downloads the update ~10 s after launch and installs it on quit. Move
%LOCALAPPDATA%\antigravity-updater\pendingaway and replace it with an empty read-only file namedpending. The updater then fails withEEXIST ... mkdir pendingand leaves the installed version alone. - Optional:
VACUUMof large conversation DBs. One went from 1226 MB to 504 MB with identical row counts andintegrity_check = ok.
Additional issues noticed along the way
language_server.logis truncated on every restart, so the crash dump is lost as soon as auto-restart kicks in. Keeping the previous log (e.g.language_server.prev.log) would make this much easier to diagnose.- The summaries reconciler references conversations that are “not found” even though their
.dbexists on disk. - Conversation DBs become heavily fragmented (about 60% free space inside pages, with an empty freelist). Periodic compaction, or a size warning in the UI, would help.
- The auto-updater produces an
UnhandledPromiseRejectionWarningwhen it cannot create its cache directory.
I can share the full crash snapshots privately if that helps.