micro-editor / micro-editor/micro
closed instances eat my memory
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
Regularily, one to three times a day, an instance of micro I already closed starts eating away all my memory, and I need to kill. It doesn't impact the opened instances.
It's been like that for more than a month. Has someone faced this problem ?
Specifications
Version: 2.0.10
Commit hash: b9763856
Compiled on May 01, 2022
OS: Endeavoros
Terminal: foot version: 1.12.1 +pgo +ime +graphemes -assertions
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
No source file, test, or entry point is named. Start by reproducing the memory growth with micro 2.0.10 on EndeavourOS using foot, then narrow down which closed instance remains active. Done means identifying and fixing the cause and verifying that closed instances no longer consume unbounded memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100