100% CPU load on keybase process after wake-up from standby
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Keybase GUI Version: 4.0.0-20190508150240+6614a49937
On linux, using kernel 5.1.2, keybase process uses 100% cpu on 1 core after wake-up from standby. Killing the process fails and filling it with signal SIGKILL (-9) renders it and unstoppable. The fuse mountpoint is then still mounted. The only remedy then is to reboot the laptop.
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
Start by reproducing the issue on Linux with kernel 5.1.2: suspend and resume, then observe the keybase process, its CPU use, SIGKILL behavior, and the FUSE mountpoint. Done means the post-wake process does not become an unstoppable 100% CPU process and the FUSE mount can be cleanly unmounted without rebooting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100