openstreetmap / openstreetmap/mod_tile
Examine memory usage for potential leaks
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 318
- Forks
- 199
- PR merge metrics
- No merged PRs in 30d
Description
Continuation of discussion started here: https://github.com/openstreetmap/mod_tile/issues/181#issuecomment-2164503429_
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 reading the discussion linked from the issue, especially the referenced comment, to understand the suspected memory leak and any prior findings. Determine what memory-usage evidence is needed and consider the work complete only when the suspected leak is identified or ruled out with documented results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100