Critical Regression: Antigravity IDE Single Agent causes 130GB Memory Leak / 100% CPU Idle Loop and macOS Kernel Panic on M4 Pro

I am reporting a severe, system-terminating memory leak and CPU thrashing issue directly within the Antigravity IDE. Running a single agent workflow inside the editor completely destabilizes the OS and has forced 10 consecutive macOS kernel panics/hard reboots.

Even while the agent is completely idle, the IDE’s background runner immediately spikes to 100% CPU utilization. Concurrently, the IDE’s memory allocation balloons rapidly, hitting over 130 GB of RAM allocation. Because the host machine has 64GB of physical unified memory, the IDE aggressively forces over 65GB of SSD swap allocation until the macOS kernel watchdog times out and panics the system.

Additional Context: This catastrophic failure happens during a completely trivial task: generating a codebase report on a basic, 10-file project.

Environment & Hardware Details:

Device: Mac mini (M4 Pro)

Physical Memory: 64 GB Unified RAM

OS: macOS (Apple Silicon Architecture)

Application: Antigravity IDE (Single agent task)

I too can attest to this grievance; ultimately, I was compelled to abandon the IDE, as it had become intolerable.

I’m also having 100% CPU utilization merely running the IDE without doing anything, running on Linux instead of MacOS

I have the same issue.

I also had the same issue with my machine , Macbook Air M5

I had the same issues in MacBook Pro 2019 15 inch

I also had the same issue with my machine , MacBook Pro M1 Pro.

It is because of the new antigravirty’s SECURE CODE built in extension.

I have the same problem.

Hi @salvatorecorvaglia,

This issue is resolved in Antigravity IDE 2.0.4. Please update to the latest version and let us know if you encounter any further issues.

@chunduriv ok, updated, but I can’t find SecureCoder anymore.

Hi @salvatorecorvaglia,

The Secure Coder extension caused the memory exhaustion issues in version 2.0.3 and it has been removed in the latest release. Are you still seeing any memory issues on the new version?

Everything is ok now. Thanks.