profile memory usage
Open
Nobody has claimed this yet.
performance
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
capa reliably takes up 1.5GB RSS and 2.5GB VM during processing or linting. who is using all this memory? is there any way we can bring that usage down?
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
Start by profiling capa during executable processing and linting to identify what accounts for the reported 1.5GB RSS and 2.5GB VM usage. Document the main sources of memory consumption, then verify that the usage is reduced without breaking processing or linting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100