How to find memory leak in mapboxgl
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
**mapbox-gl-js version**:2.9.1
### Question
Recently, I encountered a difficult problem, that is, frequently calling source SetData. I think this may be the reason why the memory keeps growing, which is more serious and fast on Safari. How can I troubleshoot this problem step by step. I lack experience in this field
### Links to related documentation
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
The issue concerns Mapbox GL JS 2.9.1 and repeated source.setData calls, with memory growth reported as worse in Safari. Start by reviewing the existing help documentation and reproducing the behavior in Safari if possible. Done would be a documented, step-by-step troubleshooting path or a clearly confirmed explanation of the memory growth.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- computer-graphics, web-dev
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100