[BUG] semgrep-core-proprietary spikes CPU to 100% / hangs system on macOS

Hi,

I am experiencing a severe performance issue immediately after opening Antigravity 2.0 on macOS.

Steps to Reproduce:

  1. Open the Antigravity 2.0 workspace/project on macOS.
  2. Monitor system performance using Activity Monitor or top.

Expected Result:
The platform should initialize normally without freezing the host machine.

Actual Result:
Upon opening, a background process named semgrep-core-proprietary triggers an intense execution loop (running millions of times). It spikes CPU usage to nearly 500% (or maxes out an entire core), causing extreme system lag and making the macOS UI completely unresponsive, bringing the laptop to the brink of freezing.

Environment Context:

  • Platform: Antigravity 2.0
  • Impacted Process: semgrep-core-proprietary (likely linked to the internal static analysis / language server)
  • OS: macOS

It seems like the static analysis engine is getting caught in an infinite loop, possibly failing to skip heavy directory trees, build artifacts, or recursive symlinks on macOS.

The only temporary workaround right now is forcefully killing the process via pkill -f semgrep-core-proprietary in the terminal. Any insights or hotfixes for this? Thanks!

This happens expensively with bigger codebases. Antigravity IDE process ate about 190GB or RAM yesteday so much so that my Mac showed me the Beach Ball of Death and Finder crashed because of full HDD.

Just had it happen too with Antigravity 2.0 on macOS (15.7.7) multiple semgrep-core-proprietary processes 800mb+ each (30+) eating away my memory

/Users/name/Library/Application Support/Antigravity IDE/User/globalStorage/google.securecoder/bin/darwin_arm64/semgrep-core-proprietary

its seems to be an issue with the new “securecoder” extension

Disabling the “SecureCode” extension will fix this.

Hi @Mazafard,

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.