Memory spike to 12GB when reviewing changes
Resolved 💬 3 comments Opened Jan 30, 2026 by hemezh Closed Feb 3, 2026
Description
Claude Code sessions spike to ~12GB memory usage when asking to review current changes (e.g., "review current changes"). The process becomes unresponsive and must be force-killed.
Environment
- Claude Code version: 2.1.25
- OS: macOS (Darwin 25.2.0)
- Platform: darwin arm64
Steps to Reproduce
- Start a Claude Code session
- Ask to "review current changes" (git diff review)
- Observe memory usage spike to ~12GB within seconds
Expected Behavior
Memory usage should remain reasonable (<1GB) during code review operations.
Actual Behavior
- Memory spikes to 11-12GB almost immediately
- Process becomes stuck/unresponsive
- Multiple sessions can accumulate, each consuming ~12GB
- Must force-kill with
kill -9 <pid>
Screenshots
Multiple Claude Code 2.1.25 processes showing 11.46-11.58 GB memory usage in Activity Monitor.
Additional Context
- Issue occurs repeatedly and consistently
- Happens even with relatively small changesets
- MCP servers (chrome-devtools-mcp, browsermcp) were active but unclear if related
Workaround
Force-kill the process:
ps aux | grep claude | grep -v grep | awk '{print $2, $6/1024 " MB"}'
kill -9 <pid>This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗