[Bug] High CPU usage when opening menu list with "/"
Status Fixed / completed
Maintainer reply None cached
Activity 7 comments · opened Dec 21, 2025 · closed Dec 29, 2025
Bug Description
High CPU usage when opening menu list with "/"
Environment Info
- Platform: linux
- Terminal: alacritty
- Version: 2.0.75
- Feedback ID: ebedc334-2f27-48a7-99d8-874b70334f43
Errors
[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/lunar/.local/share/claude/versions/2.0.75 (expected in multi-process scenarios)\n at W3$ (/$bunfs/root/claude:2427:2165)\n at _TA (/$bunfs/root/claude:2427:1885)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-12-21T16:49:49.645Z"},{"error":"SyntaxError: JSON Parse error: Property name must be a string literal\n at <parse> (:0)\n at parse (unknown)\n at <anonymous> (/$bunfs/root/claude:77:751)\n at A (/$bunfs/root/claude:11:6978)\n at SJ1 (/$bunfs/root/claude:2560:26855)\n at async yxD (/$bunfs/root/claude:2560:29641)\n at processTicksAndRejections (native:7:39)","timestamp":"2025-12-21T16:49:50.157Z"}]
7 Comments
---
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
---
Confirming this. CPU spikes for me when opening the menu with "'/". It remains high as long as the menu is displayed. Fan spins up. When deleting the "/" (backspace) the CPU usage instantly drops back to 0%.
Platform: linux
Terminal: ghostty
Version: 2.0.75
I may have duplicated a bug report mentioned above but with a bit more detail. Interestingly you seem to be on linux and not WSL2, which Is where I assumed the problem might be. Are either of you use linux via wsl2?
Pure Arch Linux.
Great details btw - will close mine, referencing yours.
More details here: https://github.com/anthropics/claude-code/issues/15689#issue-3767372595
Thanks, much appreciated - hopefully it'll help!
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.