kbfsdokan.exe has a memory leak
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
How to reproduce:
- Compressed a folder using the 7zip integration of TC4Shell
- Select the KBFS Drive as Output (my public Folder in this Case)
- Wait an Hour till the compression is done
- Wait more time till kbfsdokan eats so much Memory that you wont belive it
To be said, this is the first Time i am experiencing this. Killing the Process fixed it for now, still ime wondered why it leaked.
When running regulary, kbfsdokan takes around 350-400k
Win 10 64
Keybase GUI Version: 5.1.1-20191211174240+15bbb94c23
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 concerns kbfsdokan.exe on Windows 10 and gives a reproduction involving TC4Shell, 7zip integration, and the KBFS Drive. Start by reproducing the long compression run and monitoring kbfsdokan memory; no source file or test is named. Done means identifying and correcting the leak so memory does not continually grow during this workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100