herald memory leak / oom
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Herald process grows to use up all memory, then ooms, and sometimes the other containers won't come back up, requiring manual intervention.
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 Herald process growth described in the issue and monitor its memory use until the out-of-memory condition occurs. Trace the process behavior and container recovery path; done means identifying the leak and confirming that Herald no longer exhausts memory or prevents the other containers from returning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100