Memory leak on POSMAPOSL?
A pull request for this has already been merged.
- #631 by @KrisThielemans — merged
- Dominant language
- C++
- Stars
- 160
- Forks
- 113
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
When I run POSMAPOSL, I can see that the RAM used slowly increases in each iteration, by a few megabytes, about 200 in my particular example (Discovery MI, 10 time-frames).
I discovered this by running the code in a machine with limited memory, and after several iterations, it would crash, as my expectation of used memory was only valid in the few first iterations.
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 reproducing POSMAPOSL with the reported Discovery MI example and 10 time-frames while monitoring RAM across iterations. Review the discussion and linked pull request #631 for existing investigation. Done means memory usage no longer grows until the process crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100