Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude Code Memory leak after startup

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

After starting ClaudeCode, the process exhibits a consistent memory leak. Monitoring shows memory usage increasing at a rate of approximately 30MB per second. This continues until system resources are exhausted. The issue is reproducible across multiple restarts. Only on vscode integrated terminal

What Should Happen?

nothing

Error Messages/Logs

Steps to Reproduce

Launch ClaudeCode.

Observe memory usage via system monitor or profiler.

Note that memory consumption grows steadily at ~30MB/s.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.113 (Claude Code)

Platform

Other

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

extent analysis

TL;DR

The memory leak in ClaudeCode when run in the VS Code integrated terminal on Windows may be related to a regression introduced in version 2.1.113, and investigating the differences between this version and the last known working version could provide insight into the cause.

Guidance

  • Investigate the changes made between the current version (2.1.113) and the last working version to identify potential causes of the memory leak.
  • Run ClaudeCode in a standalone terminal outside of VS Code to determine if the issue is specific to the integrated terminal environment.
  • Monitor system resources and memory allocation to better understand the pattern of the memory leak and identify potential bottlenecks.
  • Consider reaching out to the development team or community for assistance in identifying the last working version, as this information is not provided.

Example

No specific code example can be provided without more information on the changes made in version 2.1.113.

Notes

The lack of information on the last working version and the specific changes made in version 2.1.113 limits the ability to provide a precise fix. Additionally, the issue being specific to the VS Code integrated terminal on Windows suggests that the problem might be related to the interaction between ClaudeCode and the terminal environment.

Recommendation

Apply workaround: Run ClaudeCode in a standalone terminal outside of VS Code until the issue is resolved, as this may mitigate the memory leak if it is environment-specific.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#prompt issue#agent setup#task chaining#parallel task#memory leak

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Claude Code Memory leak after startup