kbfs went to 100% CPU, macOS became unusable except for Finder
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I was doing something normal with the keybase UI popup (not sure what, but probably related to opening a /keybase/private/ folder), when:
- clicking on the menu-bar KB icon caused the popup to popup for a split second, then disappear, returning me to the Finder
- clicking on any other application window cause that application to get focus for a moment, then focus returned to the Finder
- I could scroll other applications (a web browser), and I could register one click (e.g. to select a different tab), but then the Finder would get control again
- the
kbfsprocess was wedged, and the macOS Activity Monitor reported it at 260% CPU
Logs are referenced below. I Force-Quit the KeyBase.app process, then restarted it, which seems to have fixed things. Let me know if there's more I can do to track it down.
my log id: 67975e4fe80a4e1db9cf081c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names the kbfs process, Keybase.app, macOS Activity Monitor, and log ID 67975e4fe80a4e1db9cf081c, but no source file, test, or reproducible trigger. Start by examining the referenced log and the reported kbfs behavior; the issue does not define a specific change or completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100