Highlight memory leak cycles
Open
enhancement
help-needed
- Dominant language
- Python
- Stars
- 840
- Forks
- 72
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice to highlight the cycles that are responsible for memory leaks. It would also be nice to highlight objects that are solely preventing large amounts of memory to be gc'ed. I am thinking of a dominator analysis
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points to inspect. It proposes dominator analysis to identify cycles responsible for memory leaks and objects preventing large amounts of memory from being garbage-collected. Done would mean those objects or cycles are highlighted in the object-graph output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100