[Bug] High CPU usage during execution
Status Closed — not planned
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 11 comments · opened Nov 24, 2025 · closed Jan 25, 2026
Bug Description
Using hundreds of percent CPU bullshit again
<img width="270" height="70" alt="Image" src="https://github.com/user-attachments/assets/55c8429b-36c6-4444-bd38-57248df4ab14" />
You've just closed the ticket and said that you've fixed it and it's working. No, you haven't. It doesn't work. It's using hundreds and hundreds of percent of CPU just on 1 instance. It didn't do this. Many versions ago, you could run 8 of them or ten of them just fine. Now you can't even run 1 without it completely taking the machine down.
Environment Info
- Platform: darwin
- Terminal: tmux
- Version: 2.0.50
- Feedback ID: e4184a19-f7be-4c4c-90d4-348ac21b7d25
Errors
[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-23T08:23:47.465Z"},{"error":"TypeError: A boolean was expected\n at unknown\n at <anonymous> (/$bunfs/root/claude:836:36859)\n at new Promise (native:1:11)\n at tT8 (/$bunfs/root/claude:836:36839)\n at uHR (/$bunfs/root/claude:836:80025)\n at async gtR (/$bunfs/root/claude:836:84931)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-23T08:46:08.887Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-23T08:53:48.126Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-23T09:23:48.169Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-23T09:53:47.491Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-23T10:23:47.709Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-23T10:53:47.517Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-23T11:23:47.428Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (/$bunfs/root/claude:2641:12469)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-11-23T11:53:48.112Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/greg/.local/share/claude/versions/2.0.50 (expected in multi-process scenarios)\n at JL0 (/$bunfs/root/claude:2641:1622)\n at b_A (/$bunfs/root/claude:2639:12709)\n at async pA7 (/$bunfs/root/claude:2639:13911)\n at async Ex (/$bunfs/root/claude:2641:236)\n at async <anonymous> (
Note: Error logs were truncated.
11 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
No, all you keep doing is saying it's solved and that the duplicates It's absolutely ridiculous this, it's non-stop, hundreds and hundreds of percent. This has been going on far too long, it needs fixing.
<img width="519" height="129" alt="Image" src="https://github.com/user-attachments/assets/8692f27e-ff50-4124-b915-0249c339b107" />
This is constant
<img width="558" height="1448" alt="Image" src="https://github.com/user-attachments/assets/8e0a20cb-750a-4fa1-b7d3-8ad49668a52a" />
It just repeats the same thing over and over again. Going up and down the screen.
<img width="543" height="1027" alt="Image" src="https://github.com/user-attachments/assets/e820f8d6-c052-49fc-a865-dd625eb5b5dd" />
<img width="512" height="258" alt="Image" src="https://github.com/user-attachments/assets/32b5bb2b-4c8a-4eee-a9cf-ec2e37287c20" /> All these random characters keep coming up all the time when you type anything.
2.0.50 is very buggy, causing lag and it seems to edit entire file instead of targeted edits. Multiple bugs were reported on this.
So the workaround is to rollback to 2.0.49
Steps:
<img width="327" height="109" alt="Image" src="https://github.com/user-attachments/assets/20434566-4a9f-457d-86a2-ae6c5c3553be" />
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
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.