Bug Report: Language server crashes with "index out of range" after Electron exit crash on CachyOS/Arch Linux

Google Antigravity
,
1

SUMMARY

Antigravity’s language server crashes on startup with a panic after Electron
crashes during exit. The crash corrupts code_tracker binary files, which causes
subsequent launches to fail.

SYSTEM INFORMATION

  • OS: CachyOS (Arch Linux)
  • Antigravity Version: 1.16.5-1 (AUR package)
  • Electron Version: 39
  • Installation Method: AUR package (antigravity)

STEPS TO REPRODUCE

  1. Open Antigravity and work normally
  2. Close Antigravity (File → Quit or close window)
  3. Electron crashes on exit with SIGSEGV (visible in coredumpctl)
  4. Reopen Antigravity
  5. Language server crashes immediately with panic

EXPECTED BEHAVIOR

  • Antigravity should close cleanly without Electron crashes
  • If code_tracker data is corrupted, language server should handle gracefully
    (skip/delete corrupted files)

ACTUAL BEHAVIOR

Language server panics with:

panic: runtime error: index out of range [65533] with length 60030

goroutine 116 [running]:
google3/third_party/golang/dmp_diff/diffmatchpatch/diffmatchpatch.(*DiffMatchPatch).DiffCharsToLines(…)
third_party/golang/dmp_diff/diffmatchpatch/diff.go:452 +0x305

ROOT CAUSE ANALYSIS

  1. Electron crashes on exit (SIGSEGV) - see coredump logs
  2. Crash corrupts binary files in ~/.gemini/antigravity/code_tracker/active/
  3. Next launch: DiffMatchPatch library tries to process corrupted data
  4. Panic occurs when hitting corrupted byte (0xFFFD) interpreted as array
    index 65533

WORKAROUND

Delete code_tracker before each launch:
rm -rf ~/.gemini/antigravity/code_tracker/*

ADDITIONAL INFORMATION

  • After system reboot, issue doesn’t occur (suggests something cleans
    corrupted data)
  • Electron crashes visible in coredumpctl: multiple SIGSEGV errors on exit
  • All code_tracker files show as “data” (binary format) instead of text
    when checked with ‘file’ command
1 Like