[BUG] claude doctor hangs indefinitely, uses 100% CPU, and soft locks terminal session
Resolved 💬 20 comments Opened Aug 28, 2025 by marty0678 Closed Aug 29, 2025
💡 Likely answer: A maintainer (ant-kurt, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform (select one):
- [x] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other: <!-- specify -->
- Claude CLI version: 1.0.95
- Operating System: Windows 11 and Ubuntu WSL
- Terminal: PowerShell and bash
Bug Description
Running 1.0.93 from a fresh terminal window, running the command claude doctor worked successfully. Once Claude is updated to 1.0.95, the same command soft locks your computer. As your CPU is 100% utilized, the terminal will not respond to anything, and the command seems to hang indefinitely, as if it's in a recursive loop.
If you run it while inside Claude using the /command, it appears to work. It's only when you run it outside a running Claude session.
Can reproduce in both WSL and Windows, and node 20 and 22.
Steps to Reproduce
- Update to 1.0.95
- Run
claude doctor
Expected Behavior
It to return the results of doctor.
Actual Behavior
Hangs forever, CPU jumps to 100%, terminal soft locks.
Additional Context
Can confirm it was fine with 93 as it ran correctly on 93, right before I updated to 95.
20 Comments
I have the same problem, and the command fails:
Last login: Thu Aug 28 11:29:37 on ttys002
/etc/zprofile:7: fork failed: resource temporarily unavailable
/Users/bytedance/.zprofile:2: fork failed: resource temporarily unavailable
/etc/zshrc:7: fork failed: resource temporarily unavailable
/Users/bytedance/.oh-my-zsh/oh-my-zsh.sh:43: fork failed: resource temporarily unavailable
nvm_auto:13: fork failed: resource temporarily unavailable
compdef:95: fork failed: resource temporarily unavailable
/Users/bytedance/.zshrc:124: fork failed: resource temporarily unavailable
WK0M2R63WP%
I'm currently experiencing the same issues, and it will crash my entire computer due to insufficient memory.
The quick escape right now is:
pkill -f claude(from another tab, as the first one will be busy), hopefully we're getting a fix soonThe same on my side, OS: Mac OS 15.6 on M1 Pro, terminal oh my zsh
Same problem. Just tried to run doctor and had to hard restart my laptop, event mouse cursor was laggy.
"Checking installation status…"
mds_store process raised to hundreds of CPU.
MacOS 15.4.1 (24E263)
1.0.95 (Claude Code)
Have observed the same on both Wndows and Linux. On Linux I noticed a large amount of "which" processes.
On MacOs it "feels" like overloading filesystem. Maybe it tries to checm content of node_modules somehow and got into a blackhole.
Same issue here.
Same issue with 1.0.96 on macOS 15.6.1 in Terminal.app.
Terminal hangs, shell scripts stop working across the board, there is a process named
1.0.96using ~100% CPU in Activity Monitor. Computer just becomes slow across the board. Trying to create a new Terminal tab yields:Same issue here (same configuration as what @rben01 posted above).
Same issue here.
MacOS 15.4.1 (24E263)
1.0.95 (Claude Code)
same issue here
same issue here
Windows 10
1.0.96
Same here on Linux/NixOS. It seems to get stuck in an infinite loop spawning thousands upon thousands of
npmprocesses:same here, as reported, Ubuntu 20
Same here.
Win11
Claude 1.0.96
experienced the same - seems to be when running the
claude doctorcommand but not when using the/doctorcommandEDIT: for me it's the .96 version
This should be resolved in 1.0.98, released today.
Yeah I’m still seeing 2-2.5GB RAM on an M4, per session.
So running 2-3 in parallel is making my machine feel sluggish.
On Wed, Sep 3, 2025 at 6:52 PM Slava Vishnyakov @.***>
wrote:
I have the same issue, running top in wsl shows infinite "npm config get" processes
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.