Skip to content

[Bug]: !!!IMPORTANT!!!!!!---Antigravity ACP (agy_acp_server.exe) leaks gigabytes of orphaned _MEI temp directories on Windows (324+ GB) #12096

Closed
Closed
[Bug]: !!!IMPORTANT!!!!!!---Antigravity ACP (agy_acp_server.exe) leaks gigabytes of orphaned _MEI temp directories on Windows (324+ GB)#12096
Labels
bugSomething is broken or behaving incorrectly.duplicateThis issue or pull request already exists

Description

@pkreddy8223
pkreddy8223
opened on Sep 16, 2026

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

  1. Open T3 Code IDE on Windows with Antigravity ACP enabled.
  2. Use Antigravity ACP across multiple sessions/prompts or restart the IDE/sessions over a few days.
  3. Check %LOCALAPPDATA%\Temp (C:\Users\<username>\AppData\Local\Temp).
  4. Observe hundreds of leftover _MEIxxxxxx directories that never get deleted.

Expected behavior

The Antigravity ACP server should either run from a fixed cached directory or ensure its temporary runtime files are cleaned up upon termination, without leaving hundreds of gigabytes of orphaned files in %TEMP%.

Actual behavior

Every launch of agy_acp_server.exe extracts ~1.16 GB (8,247 files) into a new %TEMP%\_MEIxxxxxx folder.
When T3 Code terminates or restarts the subprocess, PyInstaller's exit handler is bypassed, leaving the entire 1.16 GB folder permanently orphaned. Over 3 days of usage (~283 runs), this accumulated 324 GB and 2.25 million files in %TEMP%.

Impact

Major degradation or frequent failure

Version or commit

Every version (Nightly, Normal one)

Environment

Windows 11 Home 64-bit (Build 26200), T3 Code Desktop, Provider: Antigravity ACP (agy_acp_server.exe)

Logs or stack traces

Directory Analysis of %LOCALAPPDATA%\Temp:
- Found 283 orphaned folders matching `_MEI*`
- Total Size: 323.29 GB
- Total Files: 2,239,559 files
- Each folder contains: `agy_acp_licenses.txt`, `python310.dll`, grpc, pydantic, websockets (~1.16 GB / 8,247 files per folder)
- Binary producing the leaks: ~/.t3/tools/antigravity-acp/win32-x64/versions/47cb50eef14f0a4655d78cfcfda869bcea7aaee5f9787e936bc2935ea612c3b8/agy_acp_server.exe (SHA256: 74ee0984927af43bc9e7917004cd1ac6674c7d8c13420be2afa0452856a56818)

Screenshots, recordings, or supporting files

Screenshot 2026-09-16 203832.png
Screenshot 2026-09-16 203911.png
Screenshot 2026-09-16 203929.png

Workaround

Manually delete the leftover _MEI* folders in %LOCALAPPDATA%\Temp using PowerShell:
Get-ChildItem $env:TEMP -Directory -Filter "_MEI*" | Remove-Item -Recurse -Force
Note: This also causes heavy cold-start latency on the first chat message as the 1.16 GB / 8,200+ files must be decompressed to disk before each new session starts.

Activity

  1. pkreddy8223
    added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Sep 16, 2026

  2. GoblinRules commented on Sep 16, 2026

    @GoblinRules
    GoblinRules
    on Sep 16, 2026

    Additional evidence from an affected Windows x64 installation inspected on 16 September:

    • T3 Code 0.0.41-nightly.20260914.1707, commit 9375c779707f.
    • Managed ACP agy_acp_server_1.1.1.
    • Approximately 28 GiB of _MEI* contents were present; complete ACP extractions were approximately 1.16 GiB / 8,247 files and contained agy_acp_licenses.txt. One small non-ACP _MEI directory was included in the overall total.
    • The retained traces had 16 checkAntigravityProvider invocations: 15 returned Success and one was interrupted. The provider cache reported ready/authenticated. The successful outer span alone does not establish every internal request succeeded, since the check converts failures into status metadata.
    • Multiple probe start times aligned with extraction folder modification times. Inspection of the installed bundle found scoped probes followed by Windows taskkill /T /F in the child-process finalizer. No matching ACP Windows crash reports were found in the last two days. This supports forced probe teardown rather than requiring spontaneous agent crashes to explain the buildup.

    This installation predates the fix merged in #12008 at 2026-09-16 02:02 UTC, which closed #9650. These observations are evidence from the old build, not a report of a regression after #12008. The fix removes process-based health probes and scopes runtime temporary directories, addressing the inspected lifecycle. A post-update Windows validation has not yet been performed here.

    No raw logs or user-specific paths are attached. Existing leftover folders have now been cleaned up separately and their absence verified.

  3. juliusmarminge commented on Sep 16, 2026

    @juliusmarminge
    juliusmarminge
    on Sep 16, 2026
    Member

    Duplicate of #9650 — fixed in #12008 (Antigravity health checks no longer spawn the PyInstaller binary; temp dirs are isolated and cleaned). Closing as superseded; reopen if you still see _MEI growth on a build that includes #12008.

  4. juliusmarminge
    closed this as completedon Sep 16, 2026
  5. juliusmarminge
    added
    duplicateThis issue or pull request already exists
    and removed
    needs-triageIssue needs maintainer review and initial categorization.
    on Sep 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions