When running a Flutter application targeting an active iOS Simulator daemon via the integrated terminal, the IDE fails to propagate proper termination signals (SIGINT/SIGTERM) to the spawned child processes upon task completion, cancellation, or hot-restart. Over a short period, thousands of orphaned zombie processes (Z status) pile up in the process tree, resulting in critical system resource exhaustion (memory ballooning to 45GB+ via memory swap, high thread count, and massive CPU spikes).
nvironment:
-
OS: macOS (Apple Silicon / Intel)
-
IDE Version: Antigravity 2.0+
-
Framework: Flutter (using target iOS Simulator
-d <SIMULATOR_ID>)
Steps to Reproduce:
-
Open a Flutter project inside Antigravity.
-
In the integrated terminal, execute a local build command targeting an iOS Simulator:
flutter run --dart-define-from-file=.config/config_local.json -d <SIMULATOR_ID> -
Terminate or restart the run sequence repeatedly within the terminal session.
-
Check system activity via
htopor the macOS Force Quit menu.
Expected Behavior:
The IDE terminal wrapper should cleanly kill the child process tree and release simulator daemon handles when the terminal process finishes or resets.
Actual Behavior:
Child processes like assetsubscriptiond linger as zombie processes (Z), accumulating virtual memory overhead under the parent Antigravity IDE process until the system triggers an “Out of Application Memory” crisis.
