keybase / keybase/client

High memory usage for io.keybase.ossifrage: 3.7 GB process

Open
#18,340 4 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

My io.keybase.ossifrage process is chewing up more memory than my 4 GB chromebook has available, so I'm deep in swap.

ps aux|grep -i keyba
chronos  22437  0.6  9.5 2675208 375796 ?      Ssl  Jun27 121:42 /usr/local/bin/keybase --debug --log-file 
 /home/chronos/user/.cache/keybase/keybase.service.log service --chdir /run/chrome/keybase --auto-forked
665416   27241  0.6 11.1 3835324 440624 ?      Sl   Jun25 143:28 io.keybase.ossifrage

What is causing this?

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 by reproducing the reported memory use on a 4 GB Chromebook, using the provided ps output as the baseline for io.keybase.ossifrage and the keybase service. Trace which process grows and identify the cause; done means the cause is documented and memory usage is corrected or the issue is explained with supporting evidence.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.