Latest Antigravity update causes runaway semgrep-core-proprietary processes, overheating, and freezes on Mac M4 Pro

Google Antigravity
, ,
1

After the latest Antigravity update, my MacBook Pro M4 Pro (24GB RAM) becomes nearly unusable after only 1–2 queries.

Symptoms:

  • severe overheating
  • UI lag/freezing
  • typing delays
  • system becomes unresponsive
  • CPU usage reaches 90%+
  • process count explodes from ~700 to 4000+
  • threads increase from ~2800 to 6300+

Activity Monitor shows thousands of repeated:

semgrep-core-proprietary

processes spawning continuously.

This strongly appears to be a runaway indexing/scanning worker loop introduced in the latest update.

What I tried:

  • restarting Antigravity
  • restarting macOS
  • force killing semgrep processes
  • closing projects

Issue consistently returns after running queries.

Environment:

  • MacBook Pro M4 Pro
  • 24GB RAM
  • latest macOS
  • latest Antigravity version

Attached screenshots clearly show:

  • runaway semgrep-core-proprietary spawning
  • CPU saturation
  • massive thread/process spikes
  • system becoming unstable

Killing semgrep processes temporarily restores responsiveness.

Would appreciate investigation from the Antigravity team because this can fully freeze the machine and cause severe thermal load.

2

same here on mac mini M2 pro. after few queries I have to force cloce my mac.

3

Same here. M4 48GB.

If you are stuck, run this command in the terminal.

sudo killall -9 semgrep-core-proprietary

4

Same here. I tried on linux and 2 Windows machines and all freezed when fixing the issues found by secure coder

5

I am seeing a very similar issue on my MacBook Air M2 (8GB/256GB).

After recent updates, Antigravity becomes unresponsive during large codebase analysis tasks. Normal editing works fine, but prompts such as full-project architecture reviews, security scans, or deep codebase analysis often cause UI freezes.

In my case, CPU and memory usage do not appear excessive, but the IDE UI hangs and sometimes requires a force quit.

I have already tried:

Restarting Antigravity

Restarting macOS

Rebuilding Python environments

Disabling heavy workspace indexing where possible

Reducing SecureCoder from Deep to Quick

It would be helpful to know whether this is related to a recent indexing/analysis engine update or a known macOS issue.

6

Found a fix:
Open user settings.json and remove every line related to securecoder and restart the IDE(restart if semgrep tasks are still running…better) till a fix is deployed for silicon macs, this works totally fine for me.

Haven’t tried on windows yet, but i am sure it will work.

Thanks and enjoy

7

That was awesome thank you. :blush:

8

Hey All,

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.