keybase / keybase/client

Seeing constant CPU usage

Open
#2,344 7 comments 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

I polled a bit this morning, approximately every five minutes for about an hour, and found that the CPU usage of the Keybase client was around 16%. No files uploading, no obvious user-generated activity.

I'll continue to monitor it, but I figured I'd log something in case others want to monitor, too.

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

The report names no files, tests, or entry points. Start by reproducing the idle Keybase client state described and collecting comparable CPU observations; done should identify the source of the sustained usage and document a verified resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
performance
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.