Memory Leak in the New Writer and cascading to Bytes makeSlice
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Description
We have been using the ocfwriter and it keeps on adding to the RAM, and maybe isn't garbage collecting for some reason.
The only workaround we have right now is to restart the machine.
Can you help?
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
Start by reproducing the reported RAM growth in the ocfwriter, then trace how it cascades to Bytes makeSlice. Use the attached memory screenshot as the reported symptom and verify that repeated writing no longer causes unbounded memory growth before considering the issue complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100