Repository navigation
Extension causes high cpu load #70
Description
- Issue Type:
Performance - Extension Name:
claude-code-usage - Extension Version:
2.2.0 - OS Version:
Linux x64 6.8.0-134-generic - VS Code version:
1.127.0
file:///tmp/GrowthJack.claude-code-usage-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load
Activity
Carl723000 commentedon Jul 12, 2026
Thanks for the report. To locate the hot path we need the profile the VS Code prompt mentions. Could you attach:
.cpuprofile.txtfrom the "unresponsive extension" prompt,~/.claude/projects(session count / total MB)?A likely factor on Linux is the recursive
fs.watchplus a full re-parse of the log corpus on each refresh during active logging. Meanwhile you can reduce the load via the Live-refresh delay setting (raise it, or set it to Off) andenableContentAnalysis: false.🤖 Generated with Claude Code
Carl723000 commentedon Jul 18, 2026
V2.2.1 now has a release candidate in #78 for this issue. It removes the hidden 8-second active polling override, adds 60/120/300-second file-watch quiet delays, bounds first-timestamp scanning, reuses one manifest per refresh, and emits anonymous stage timings.
Please test V2.2.1 on the same Linux setup after it is published, with Live refresh delay at 2 seconds and Refresh interval at both 60 and 300 seconds. Run Claude Code continuously for about 10 minutes while observing Extension Host CPU, then use Claude Code Usage: Show Diagnostic Logs and attach only the
refresh:lines. Those lines contain numeric counts and timings only—no prompts, paths, session IDs, credentials, or raw JSONL.We will keep #70 open until the Linux result is confirmed. If CPU remains high, the next useful artifact is an Extension Host CPU profile plus the anonymous
refresh:lines.🤖 Generated with OpenAI Codex
Carl723000 commentedon Aug 1, 2026
The additional energy fix has now been merged in #83 and is scheduled for v2.2.2.
Compared with v2.2.1, it stops recurring polling, file watching, credential watching, and Claude project-tree inspection while the VS Code window is in the background. Returning to the foreground performs one immediate catch-up refresh. It also adds longer quiet delays without making manual refresh unavailable.
We will keep this issue open for the original Linux reporter's confirmation. After v2.2.2 is published, please repeat the same 10-minute Extension Host CPU check and attach the anonymous
refresh:lines if the load remains high.🤖 Generated with OpenAI Codex
Carl723000 commentedon Aug 20, 2026
Thanks again for reporting this and helping us isolate the Linux CPU problem.
The refresh-frequency and background-work problems tracked by this issue were addressed across v2.2.1 and v2.2.2: the hidden active polling override was removed, longer quiet delays were added, initial scanning was bounded, and recurring work is suspended while the VS Code window is inactive. The evidence reported in #87 indicates that these controls are working as intended.
The remaining problem has a different root cause: a single changed file can still make one refresh re-read and re-aggregate the complete corpus. That work is now tracked separately in #87.
I am therefore closing this issue as fixed for its original scope. Please follow #87 for the single-refresh-cost fix, or comment again if the original recurring/background behaviour still occurs on the current release.
🤖 Generated with OpenAI Codex