Solution to TCMalloc memory size error when it is installed Antigravity CLI in Chromebook with linux arm/64

Google Antigravity
1
2

here a document with step to step, special thanks to Gemini by create this document

[Guide] Fix Google Antigravity CLI “MmapAligned() failed / Aborted (core dumped)” on ARM64 Chromebooks

If you are trying to install or run the Google Antigravity CLI (agy) inside a Linux container (Crostini/Baguette) on an ARM64 Chromebook (such as MediaTek Kompanio or Snapdragon chips) and getting an immediate crash, you are not alone.

The Problem

The official Linux ARM64 binary of Antigravity is compiled using TCMalloc configured for a standard 48-bit Userspace Virtual Address (VA) layout. However, many ARM64 Chromebook kernels restrict the userspace virtual address space to 39 bits. When TCMalloc tries to allocate memory outside boundaries, the kernel kills the process, throwing:
MmapAligned() failed - unable to allocate with tag followed by Aborted (core dumped).

Since Google hasn’t provided a native 39-bit build yet, here is a clean step-by-step workaround based on recent community patches to rewrite the binary assembly constants down to 39 bits and run it seamlessly.

Step 1: Create a Secure Patch Workspace

Set up a clean, dedicated folder inside your Linux environment to fetch the memory-patching script.

mkdir -p ~/.antigravity-patcher
cd ~/.antigravity-patcher

# Clone the 39-bit memory patcher utility script (clean URL format)
git clone [https://gist.github.com/9e97f791db704f078dcf66d0dd9245ee.git](https://gist.github.com/9e97f791db704f078dcf66d0dd9245ee.git) patch-gist

Step 2: Download the Official Unpatched Binary

Clear out any previous broken instances and download the fresh release payload directly from the Google repository.

# Clear old references
rm -f ~/.local/bin/agy

# Execute the official stable installation pipeline
curl -fsSL [https://antigravity.google/cli/install.sh](https://antigravity.google/cli/install.sh) | bash

Note: At the very end of the installer script, you will likely see an Aborted (core dumped) error. This is completely normal and expected. The installer tries to test the binary before it’s patched. The raw binary has still been placed successfully into your path.

Step 3: Patch the Binary to 39-bit Layout

Now we run the Python utility to scan instruction patterns inside the binary and shift allocation tags from bit 42 down to bit 35 (safely mapping to 39-bit limits), then create a permanent backup master file.

# Run the patcher directly against the fresh binary
python3 ~/.antigravity-patcher/patch-gist/patch_va39 ~/.local/bin/agy

# Move the newly patched artifact to a secure golden master directory
mv ~/.local/bin/agy.va39 ~/.antigravity-patcher/agy_patched_master
chmod +x ~/.antigravity-patcher/agy_patched_master

# Overwrite your active execution path with the patched working version
cp ~/.antigravity-patcher/agy_patched_master ~/.local/bin/agy
chmod +x ~/.local/bin/agy

Step 4: Inject the Self-Healing Automation Wrapper

To prevent any future system update or IDE utility from silently overwriting your functional binary with a broken 48-bit one, add an automated check to your shell configuration profile.

  1. Open your Bash configuration file:
nano ~/.bashrc
  1. Scroll to the absolute bottom of the file and paste this function block:
agy() {
    # 1. Silently test if the current active binary is throwing the 48-bit tcmalloc crash
    if ! ~/.local/bin/agy --version >/dev/null 2>&1; then
        echo "🔧 [Antigravity Wrapper] Memory allocation crash detected. Restoring master 39-bit patch..."
        
        # 2. Seamlessly restore the pre-compiled working master copy back into place
        chmod +w ~/.local/bin/agy 2>/dev/null || true
        cp ~/.antigravity-patcher/agy_patched_master ~/.local/bin/agy
        chmod +x ~/.local/bin/agy
    fi

    # 3. Pass through all command parameters natively to the working tool
    ~/.local/bin/agy "$@"
}
  1. Save and close the editor (Ctrl+O, Enter, Ctrl+X), then reload your terminal environment:
source ~/.bashrc

Step 5: Verify and Authenticate

Test that the tool responds properly without memory panics:

agy --version

Now you can launch the CLI tool normally to sign in via OAuth and start managing your autonomous development agents:

agy

Hope this saves you some hours of frustration!

***