keybase / keybase/client

Windows Clint high CPU utilization

Open
#7,085 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

The keybase.exe takes more than 95% and stops the machine from working. Keybase never reaches a point where anything else except the menu is readable. I use the latest available version.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Windows keybase.exe client and reproduce the reported sustained CPU usage that prevents normal use. Trace the client’s startup behavior until the source of the high utilization is isolated; done means the Windows client starts without monopolizing the machine.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.