If your fans spin up after 30 min of Claude Code doing nothing - it’s not CPU. It’s a memory leak -Memory (RSS) hits ~38MB/min+ with normal config -Hits 4.5 GB (would be a lot more but OSX compressing memory to keep laptop alive) within 10m -Heap stays flat at ~130MB/min - the leak is native memory, invisible to V8 GC -macOS compression hides it from Activity Monitor until it’s too late -At least 4 independent leak vectors across 15+ open GitHub issues -Affects macOS, Linux, and WSL equally. Only workaround is restarting sessions every 1-2h. Also try Disable your statusline if you have one Restart sessions every 1-2 hours. Annoying but effective. Pin to v2.1.52 if you can (CLAUDE_CODE_DISABLE_AUTOUPDATE=1) - multiple reports of it being stable. Disconnect Gmail/Google Calendar MCP servers if you have them - reported as a leak source. Update to v2.1.74+ which fixes one vector (streaming buffers not released on early generator termination). How to monitor it yourself: Run ps axo pid,rss,command | grep claude every few minutes (on mac). RSS is in KB. If it’s climbing while you’re idle, that’s the leak. I built a small Python dashboard that polls this and graphs it - happy to share if there’s interest. There are 15+ open GitHub issues documenting this. It’s not one bug - it’s at least 4 independent leak vectors. Anthropic has fixed one (streaming buffers in v2.1.74). The rest are still open. You’re welcome. submitted by /u/MarriedAdventurer123
Originally posted by u/MarriedAdventurer123 on r/ClaudeCode