livepeer / livepeer/go-livepeer
Investigate likely mem leak on B
Open
Nobody has claimed this yet.
need: investigation
need: more info
type: bug
type: tech debt
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
At one point a B has only ~17 streams (max) with 13GB of RAM usage which seems pretty fishy.
Contributor guide
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 file, test, or entry point is named. Start by reproducing the report of about 13GB of RAM with roughly 17 streams on B, then profile the process to locate the memory growth. Done means the leak is identified and a fix or clearly documented finding is provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100