[BUG] UsageMemore

Resolved 💬 3 comments Opened Mar 12, 2026 by AlexeyKharin06 Closed Mar 16, 2026

Preflight Checklist

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

What's Wrong?

Title: Memory leak ~1.4 GB/min in Claude Code CLI on Windows

Body:

Bug report

Claude Code CLI process grows in memory at ~1.4 GB/min even when idle (no tools running, no user input). Reaches 8-10 GB within 5 minutes, causing system slowdowns on 16 GB
machine.

Measurements

Fresh session, no active work:

┌──────┬────────┬─────────┐
│ Time │ RAM │ Delta │
├──────┼────────┼─────────┤
│ 0s │ 1.1 GB │ — │
├──────┼────────┼─────────┤
│ +30s │ 1.7 GB │ +0.6 GB │
├──────┼────────┼─────────┤
│ +60s │ 2.5 GB │ +0.8 GB │
└──────┴────────┴─────────┘

Previous session reached 8.4 GB before restart.

Environment

  • Claude Code: 2.1.73
  • Node.js: v24.13.1
  • OS: Windows 11 Home 10.0.26200
  • RAM: 16 GB
  • Shell: Git Bash

What Should Happen?

Memory should stabilize after tool execution completes, not grow indefinitely.

Error Messages/Logs

Steps to Reproduce

  1. Open terminal, run claude
  2. Have a conversation with a few tool calls
  3. Monitor memory: wmic process where "Name='claude.exe'" get WorkingSetSize
  4. Observe continuous growth even when idle

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.73

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗