High memory consumption causing editor lag and navigation failures (resolved by disabling extension) on MacOS

Author: ZeeshanAhmadAIOCreated Jul 15, 2026Updated Sep 17, 2026
Labelstriage

Description

I noticed significant performance degradation while working in a large NX monorepo (3 workspaces: ~120+ TypeScript files across apps and libs). Symptoms included:

  • Editor navigation functions stopped working (go to definition, find references, etc.)
  • General IDE sluggishness and lag
  • High memory usage traced to the extension host process via VS Code's Process Explorer

After disabling GitLens, all navigation functions immediately restored and editor performance improved noticeably. The TypeScript language server memory also dropped to normal levels.

Steps to reproduce:

  1. Open a large NX monorepo (multiple workspaces with many TypeScript files)
  2. Enable GitLens with default settings
  3. Work for a while — observe increasing memory via Help → Open Process Explorer
  4. Navigation functions (Go to Definition, Find References) become unresponsive
  5. Disable GitLens → navigation immediately restores

Expected: GitLens should not interfere with editor navigation or consume enough memory to degrade core editor functions.

Note: The built-in VS Code Git blame (git.blame.editorDecoration.enabled) covers the inline blame use case without any performance impact


Model: MacBook Pro (MacBookPro18,1) Chip: Apple M1 Pro Cores: 10 (8 performance + 2 efficiency) Memory: 16 GB

GitLens Version

18.2.0-universal

VS Code Version

Cursor 3.9.16 (VS Code fork) Build: 042b3c1a4c53f2c3808067f519fbfc67b72cad80 Platform: darwin arm64

Git Version

git version 2.50.1 (Apple Git-155)

Logs, Screenshots, Screen Captures, etc

No response

Source: gitkraken/vscode-gitlens