[Bug] Claude Code memory leak causing repeated crashes with Opus 4.6

Resolved 💬 2 comments Opened Mar 9, 2026 by meckdahl Closed Mar 9, 2026

Bug Description
I use largely Claude Code. Recently (last 3 weeks or so), I have started heavy use of Opus 4.6 (medium). It keeps crashing from a memory leak filling up available memory. It is leaving zombie processes that slowly eat up virtual and RAM memory it needs. I have written a prompt to clean it, but I have taken to rebooting often and documenting progress and logs in notepad because Claude is unstable and loses its progress when it crashes. It has crashed about 15 times in last 5 days, even with reboots, resets, memory cleans. here is recent good output from a cleanup command: ---
CLEANUP REPORT
------------------------------
Claude:
Status: normal
Private: 1748 MB / 4096 MB (ok)
Handles: 1417 (ok)
Action: none
Zombies: 0 found
Docker:
Status: not running (skipped)
Containers: n/a
Images: n/a
Volumes: n/a
Temp files: none (venv caches only, left intact)
Claude logs: 19.7 MB (under 20 MB threshold, no trim)
Memory: 17.2 GB free / 31.7 GB total (committed: 21.3 GB)
------------------------------
Disk recovered: 0 GB (system already clean)
Everything looks healthy. Run /cleanup again anytime.

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.71
  • Feedback ID: 0e8459c7-44de-4ca2-8558-bcd6fb6edbf5

Errors

[]

View original on GitHub ↗

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