Bug Report: Antigravity AI Language Server crashes on ARM64 Chromebook

Bug Report: AI Language Server crashes on ARM64 Chromebook due to TCMalloc 48-bit VA space assumption

Summary

The Antigravity language server (language_server_linux_arm) crashes immediately on ARM64 Chromebooks
running Crostini (Linux). The error indicates TCMalloc was compiled assuming a 48-bit virtual address
space, but ARM64 Chromebooks use a smaller VA space (~39-40 bit).

Environment

  • Antigravity Version: 1.11.5-1763627320 (arm64 .deb)
  • OS: Debian GNU/Linux 12 (bookworm) via Crostini
  • Kernel: 6.6.99-08726-g28eab9a1f61e aarch64
  • Hardware: ARM64 Chromebook (CPU implementer: 0x41, CPU part: 0xd81)

Steps to Reproduce

  1. Install Antigravity on an ARM64 Chromebook via .deb package
  2. Launch Antigravity
  3. Observe “Antigravity server crashed unexpectedly. Please restart to fully restore AI features.”

Error Details

Running the language server directly produces:
$ /usr/share/antigravity/resources/app/extensions/antigravity/bin/language_server_linux_arm --version

third_party/tcmalloc/internal/system_allocator.h:580] MmapAligned() failed - unable to allocate with tag
(hint=0x6fcd40000000, size=1073741824, alignment=1073741824) - is something limiting address placement?
third_party/tcmalloc/internal/system_allocator.h:587] Note: the allocation may have failed because
TCMalloc assumes a 48-bit virtual address space size; you may need to rebuild TCMalloc with
TCMALLOC_ADDRESS_BITS defined to your system’s virtual address space size
third_party/tcmalloc/arena.cc:59] CHECK in Alloc: FATAL ERROR: Out of memory trying to allocate internal
tcmalloc data (bytes=131072, object-size=16384); is something preventing mmap from succeeding (sandbox,
VSS limitations)?

Extension host log (~/.config/Antigravity/logs/…/exthost.log):

[error] Activating extension google.antigravity failed due to an error:
[error] Error: Language server has not been started!
at get httpPort
(/usr/share/antigravity/resources/app/extensions/antigravity/dist/extension.js:2:220079)

Root Cause Analysis

The language_server_linux_arm binary is correctly compiled for ARM64 (ELF 64-bit LSB, ARM aarch64), but
TCMalloc is statically linked with the default assumption of 48-bit virtual address space. ARM64
Chromebooks running ChromeOS/Crostini typically have a restricted VA space (39-42 bits), causing
TCMalloc’s memory mapping to fail.

Suggested Fix

Recompile the ARM64 language server binary with:
-DTCMALLOC_ADDRESS_BITS=39
Or use the system allocator instead of TCMalloc for ARM64 builds targeting Chromebook hardware.

Workarounds Attempted (None Successful)

  • LD_PRELOAD with system libc (TCMalloc is statically linked)
  • TCMALLOC_LARGE_ALLOC_REPORT_THRESHOLD environment variable
  • Permission fixes per macOS troubleshooting (not applicable - different root cause)

Impact

AI features are completely non-functional on ARM64 Chromebooks. The IDE otherwise works correctly.

10 Likes

I’m seeing same issue (Lenovo Chomebook 14 Plus) - was wondering how/where to report that for Antigravity

3 Likes

same, there doesn’t seem to be an official support channel set up yet.

1 Like

+1 on the same issue on a Lenovo Chomebook 14 Plus

2 Likes

same issue on a Lenovo Chromebook11 3180

1 Like

Running into the same problem on a Lenovo Duet…

2 Likes

have the same issue on lenovo duet 5

On EndeavourOS detto issue…

Same on Lenovo Chromebook Plus 14 ARM

Same issue on Windows11 WSL 1

Antigravity Version: 1.12.4

/lib64/ld-linux-x86-64.so.2 ./language_server_linux_x64
68 third_party/tcmalloc/internal/system_allocator.h:585] MmapAligned() failed - unable to allocate with tag (hint=0x4ed840000000, size=1073741824, alignment=1073741824) - is something limiting address placement?
68 third_party/tcmalloc/internal/system_allocator.h:592] Note: the allocation may have failed because TCMalloc assumes a 48-bit virtual address space size; you may need to rebuild TCMalloc with TCMALLOC_ADDRESS_BITS defined to your system’s virtual address space size
68 third_party/tcmalloc/arena.cc:59] CHECK in Alloc: FATAL ERROR: Out of memory trying to allocate internal tcmalloc data (bytes=131072, object-size=16384); is something preventing mmap from succeeding (sandbox, VSS limitations)?
Aborted (core dumped)