Investigate and fix memory leak in Manager
Open
- Dominant language
- Python
- Stars
- 670
- Forks
- 183
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 368
Description
A memory leak has been observed in the Manager component. Memory usage grows steadily over time and is not reclaimed.
Goal:
- Reproduce and measure the memory growth in Manager.
- Identify the root cause (retained references, unbounded caches/queues, unclosed resources, etc.).
- Apply a fix and verify that memory usage stabilizes under sustained load.
JIRA Issue: BA-6792
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reproducing and measuring memory growth in the Manager component under sustained load, then trace retained references, unbounded caches or queues, and unclosed resources; done means memory usage stabilizes after the fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100