CRITICAL: Persistent Memory Leak in LSP despite Strict Exclusion Configuration (Windows x64)

Google Antigravity
1

To the Google AI Forum Support Team,

I am following up on my previous report regarding Google Anti Gravity consuming 12.5% CPU and 13 GB RAM.

I have now implemented a full “LSP Mitigation Stack” to stop the Language Server from indexing heavy directories, but the issue persists. This confirms that the leak is not caused by my project files, but by a fundamental flaw in how the application handles its internal processes.

Key Technical Actions Taken (See attached report):

  • Root-level jsconfig.json: Explicitly excluded node_modules, backend/uploads, and build directories to act as a gatekeeper.

  • VS Code Workspace Settings: Disabled typescript.validate, javascript.validate, and npm.autoDetect. I have also strictly limited files.watcherExclude.

  • Frontend tsconfig.json: Restricted the compiler to only look at specific source folders.

Conclusion for Support: Despite these “Nuclear Option” exclusions, the application still hangs for 3-5 minutes when interacting with the terminal. This suggests that the internal TypeScript Language Server or a core component is ignoring these configuration files or is stuck in an infinite loop regardless of the defined scope.

I have attached the lsp_optimization_report.md and my main.log as proof of these efforts.

Request: Please investigate why the core services are still aggressively indexing or leaking memory (13 GB+) when all heavy directories have been explicitly excluded in the configuration.

lsp_optimization_report.md
Technical Report: VS Code Language Server Memory Leak Mitigation

Date: 2026-02-01
Issue: VS Code Language Server (LSP) consuming excessive resources (12.5% CPU, ~13GB RAM), causing system instability.
Root Cause: The TypeScript/JavaScript Language Server was aggressively indexing the node_modules directory and the backend/uploads directory (likely containing large media files), causing an OOM (Out of Memory) situation or infinite indexing loop.

Mitigation Steps Applied

The following configuration changes were applied to strictly limit the scope of the Language Server’s indexing and validation processes.

1. Root-Level jsconfig.json (New File)

Path: [Project Root]/jsconfig.json
Purpose: Acts as a gatekeeper at the project root to prevent the VS Code JS/TS service from traversing into heavy directories.
Configuration:

{
    "compilerOptions": {
        "checkJs": false,
        "allowJs": false
    },
    "exclude": [
        "node_modules",
        "Frontend/node_modules",
        "backend/uploads",
        "dist",
        "build"
    ]
}

2. VS Code Workspace Settings

Path: [Project Root]/.vscode/settings.json
Purpose: Disables non-essential language features, prevents file watching on large directories, and excludes them from search/indexing.
Key Changes:

  • files.watcherExclude: Strictly limited to source code directories. Explicitly excludes node_modules and backend/uploads.
  • typescript.validate.enable / javascript.validate.enable: Set to false to reduce CPU overhead from real-time validation.
  • git.enabled: Set to false (temporarily) to prevent Git status checks on thousands of files from consuming resources.
  • npm.autoDetect: Disabled to prevent scanning for package.json scripts in deep directories.

3. Frontend TypeScript Configuration

Path: [Project Root]/Frontend/tsconfig.json
Purpose: Ensures the frontend TypeScript compiler only looks at source code and explicitly ignores all build artifacts and dependencies.
Configuration:

{
  "include": [
    "src/**/*",
    "components/**/*",
    "contexts/**/*",
    "hooks/**/*",
    "services/**/*",
    "*.ts",
    "*.tsx"
  ],
  "exclude": [
    "node_modules",
    "dist",
    "build",
    "coverage",
    ".vscode",
    ".git"
  ]
}

Recommendation for Support

If the issue persists despite these strict exclusions, it suggests a potential bug in the specific version of the TypeScript Language Server or a conflict with an installed extension (e.g., Intelephense) attempting to index the same large directories. The current configuration represents the “Nuclear Option” for exclusion and should theoretically prevent the LSP from consuming significant resources.

Main.log
2026-02-01 11:02:29.704 [info] Using Cloud Code URL: https://daily-cloudcode-pa.googleapis.com
2026-02-01 11:02:29.704 [info] [BrowserOnboardingClientMainService] Starting browser onboarding server
2026-02-01 11:02:29.704 [info] [BrowserOnboardingClientServer] Browser onboarding server started on http://localhost:64744
2026-02-01 11:02:29.704 [info] update#setState idle
2026-02-01 11:02:31.203 [info] AntigravityAuthMainService initialized
2026-02-01 11:02:32.219 [warning] updateWindowsJumpList#setJumpList unexpected result: customCategoryAccessDeniedError
2026-02-01 11:02:59.713 [info] update#setState checking for updates
2026-02-01 11:02:59.850 [info] update#setState idle
2026-02-01 11:04:26.260 [warning] [perf] profiling STARTED dcab57a3-fa0c-4d1c-9a20-a41181a60fda
2026-02-01 11:04:31.292 [warning] [perf] profiling DONE dcab57a3-fa0c-4d1c-9a20-a41181a60fda
2026-02-01 11:04:46.488 [warning] [perf] profiling STARTED dcab57a3-fa0c-4d1c-9a20-a41181a60fda
2026-02-01 11:04:51.516 [warning] [perf] profiling DONE dcab57a3-fa0c-4d1c-9a20-a41181a60fda
2026-02-01 11:05:06.689 [warning] [perf] profiling STARTED dcab57a3-fa0c-4d1c-9a20-a41181a60fda
2026-02-01 11:05:11.714 [warning] [perf] profiling DONE dcab57a3-fa0c-4d1c-9a20-a41181a60fda
2026-02-01 11:45:27.878 [info] Extension host with pid 28220 exited with code: 0, signal: unknown.
2026-02-01 11:55:18.059 [warning] [perf] profiling STARTED 0c87a6a2-5e8b-47f6-ac82-3976018a0617
2026-02-01 11:55:23.081 [warning] [perf] profiling DONE 0c87a6a2-5e8b-47f6-ac82-3976018a0617
2026-02-01 11:55:38.282 [warning] [perf] profiling STARTED 0c87a6a2-5e8b-47f6-ac82-3976018a0617
2026-02-01 11:55:43.310 [warning] [perf] profiling DONE 0c87a6a2-5e8b-47f6-ac82-3976018a0617
2026-02-01 11:55:58.508 [warning] [perf] profiling STARTED 0c87a6a2-5e8b-47f6-ac82-3976018a0617
2026-02-01 11:56:03.532 [warning] [perf] profiling DONE 0c87a6a2-5e8b-47f6-ac82-3976018a0617
2026-02-01 12:02:59.722 [info] update#setState checking for updates
2026-02-01 12:02:59.921 [info] update#setState idle
2026-02-01 12:03:19.812 [warning] [perf] profiling STARTED e3ef0a6b-2a91-4deb-b8a0-47d33a6d7138
2026-02-01 12:03:24.848 [warning] [perf] profiling DONE e3ef0a6b-2a91-4deb-b8a0-47d33a6d7138
2026-02-01 12:03:40.077 [warning] [perf] profiling STARTED e3ef0a6b-2a91-4deb-b8a0-47d33a6d7138
2026-02-01 12:03:45.102 [warning] [perf] profiling DONE e3ef0a6b-2a91-4deb-b8a0-47d33a6d7138
2026-02-01 12:04:00.319 [warning] [perf] profiling STARTED e3ef0a6b-2a91-4deb-b8a0-47d33a6d7138
2026-02-01 12:04:05.347 [warning] [perf] profiling DONE e3ef0a6b-2a91-4deb-b8a0-47d33a6d7138
2026-02-01 12:09:22.750 [info] Extension host with pid 27080 exited with code: 0, signal: unknown.
2026-02-01 12:09:54.793 [warning] [perf] profiling STARTED 725ba774-7013-4c6d-b89b-d3a82ff04875
2026-02-01 12:09:59.814 [warning] [perf] profiling DONE 725ba774-7013-4c6d-b89b-d3a82ff04875
2026-02-01 12:10:15.258 [warning] [perf] profiling STARTED 725ba774-7013-4c6d-b89b-d3a82ff04875
2026-02-01 12:10:20.286 [warning] [perf] profiling DONE 725ba774-7013-4c6d-b89b-d3a82ff04875
2026-02-01 12:10:35.539 [warning] [perf] profiling STARTED 725ba774-7013-4c6d-b89b-d3a82ff04875
2026-02-01 12:10:40.573 [warning] [perf] profiling DONE 725ba774-7013-4c6d-b89b-d3a82ff04875
2026-02-01 12:13:18.840 [info] Extension host with pid 9628 exited with code: 0, signal: unknown.
2026-02-01 12:13:39.138 [warning] [perf] profiling STARTED 92373962-f0b0-43af-8356-7f238a1a3ca6
2026-02-01 12:13:44.158 [warning] [perf] profiling DONE 92373962-f0b0-43af-8356-7f238a1a3ca6
2026-02-01 12:13:59.549 [warning] [perf] profiling STARTED 92373962-f0b0-43af-8356-7f238a1a3ca6
2026-02-01 12:14:04.586 [warning] [perf] profiling DONE 92373962-f0b0-43af-8356-7f238a1a3ca6
2026-02-01 12:14:19.900 [warning] [perf] profiling STARTED 92373962-f0b0-43af-8356-7f238a1a3ca6
2026-02-01 12:14:24.920 [warning] [perf] profiling DONE 92373962-f0b0-43af-8356-7f238a1a3ca6
2026-02-01 12:20:28.394 [info] Extension host with pid 3320 exited with code: 0, signal: unknown.