Request to the Antigravity team. Browser scan - RAM overload, server crash. (Solution)

Google Antigravity
1

Hi, team.

When I was using the browser scan feature, it was crashing my server at first.
The reason was the RAM overload.

So, I have created the rule for the agent, and now it’s working fine without RAM overload.
Here is the rule:
______________________
AI ASSISTANT MANDATORY CLEANUP & RAM SUSTAINABILITY:

  • The AI assistant MUST clean up all background processes and free all occupied ports (3001, 3002, 3003, etc.) in the development environment immediately after finishing implementation, testing, or checkup tasks.
  • CRITICAL: Under no circumstances can the PRODUCTION mode of any app be stopped or restarted. Only the development and staging modes are permitted to be stopped for cleanup or maintenance.
  • Always verify that the service or process being killed is not associated with Production ports (3000, 3006, 3007, 80, 443).
  • TOTAL STAGING SILENCE: Before launching the browser or performing memory-heavy builds, the assistant MUST stop the Staging services (e.g., systemd -dev services) of ALL other apps on this server to reclaim RAM.
  • BROWSER ZOMBIE CLEANUP: Ensure all orphaned chrome, chromium, or playwright driver instances from previous sessions are force-killed.
  • STRICT RAM THRESHOLD: If available RAM (free -h) is below 1GB, the assistant MUST notify the USER and refuse to launch the browser or heavy builds until memory is recovered.
    ____________________________
    I am not sure if it could be somehow helpful to you guys, but this approach is working.
    The server doesn’t crash anymore and the RAM is running low, not even close to overload numbers.
    Maybe you can implement something like a small automatic cleanup before the agent uses the browser into the system.

Thank you.

P.S. Please, add more tags to the topic creation “optional tags."
It’s very limited as of right now.
I couldn’t find “server“, “ram“, “overload” tags in your system.

1 Like