Tried several options to fix the memory and slow glitchy issues. Seems downgrading back to 1.16 or a more stable version might be the only option. I assume google is working to get an update to it quickly. If I find a fix, I’ll post it here, any suggestions welcomed. Mike
1 Like
Seems to be working a little better. I did a couple of scripts. I’ll post this one first, since its easy and may help. I’m testing which one made the IDE run a ‘bit better’.
First one: To use the below script, close Antigravity then run the below script in a terminal to ‘open’ Antigravity without the GPU acceleration enabled. To reset it to normal, just close antigravity and reopen it like you normally would. The default will always be to have it ‘enabled.
The results seem to be this: I still get an error message (I’m on a new macbook air): “The window is not responding” which you can ignore. I either say “keep waiting” or just go get a cup of coffee.
The processing speed seems to work fine, but you can’t type anything in the agent while it is working, its mostly frozen. But, it does work at full speed. You just have to wait till its done thinking.
Just save the below script into a file names something like: safe_launch.sh
#!/bin/bash
# SAFE LAUNCH WRAPPER
# This script launches the IDE with GPU acceleration disabled to fix macOS lag.
# See: Electron Issue #40201 regarding WindowServer spikes.
echo "🚀 Launching IDE with --disable-skia-graphite..."
if command -v antigravity &> /dev/null; then
antigravity . --disable-skia-graphite "$@"
elif command -v code &> /dev/null; then
code . --disable-skia-graphite "$@"
else
echo "❌ Error: Neither 'antigravity' nor 'code' command found in your terminal."
echo "To fix this:"
echo "1. Go to your open IDE window."
echo "2. Press Cmd + Shift + P to open the Command Palette."
echo "3. Search for 'Shell Command: Install command in PATH' and run it."
echo "4. Come back to this terminal, close it, open a fresh terminal, and try again."
fi
1 Like
Seems I found the fix for Macbook’s, it’s an easy fix and can be reverted anytime.
Here is how you should configure specific settings to restore stability to the IDE:
1. Enable Terminal Sandbox: Disabled
You should disable this, particularly if you are developing on a Windows machine using WSL2. The 1.18.3 update contains a bug where the IDE misidentifies the host operating system and erroneously attempts to inject the macOS-specific sandbox-exec utility into Linux environments [1, 2]. This causes background commands to fail silently, which hangs the agent and contributes to the UI freezing.
2. Enable Shell Integration: Disabled (Off)
This is the most critical setting to change to fix the specific freeze you are experiencing. You must toggle this to the “Off” position [3]. By disabling it, the agent will bypass the IDE’s fragile graphical terminal parser and interact directly with the raw system shell. This completely circumvents the bug where the IDE misses command completion markers (due to terminal formatting noise) and locks up the main rendering thread [3]. Be sure to restart the application after changing this setting [3].
1 Like
How did you go about turning off sandbox command in WSL? I don’t have the option in the settings but keep getting the sandbox commands injected but can’t figure out how to turn it off.
I only use a macbook so for me I have the settings in the IDE. My information on the WSL was speculation on how to do it in a Windows, but I do not have that machine to test on. Suprising you don’t have those two settings in a windows IDE somewhere. Mine are at the bottom right in my IDA as “Antigravity - Settings”.
But I’ve been testing it all day, and it removes the logjam I had and now I can continue easily as before. Hope you can figure out how to implement it John.
Yeah the option to turn off sandboxing doesn’t appear on the windows version, which I guess makes sense but annoying when its turned on automatically lol.
Thankfully it looks like turning off shell integration seems to of fixed that issue as well and its back to working normally as long as I keep that setting off.
Thanks!
1 Like