mapbox / mapbox/mapbox-maps-flutter
Memory Leak in Map Display Component on iOS 17.1
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 380
- Forks
- 204
- PR merge metrics
- No merged PRs in 30d
Description
### Environment
- Device: iPhone
- OS: iOS 17.1
- Package: mapbox-maps-flutter
### Issue Description
I've encountered a significant memory leak issue when using the map display component of `mapbox-maps-flutter` on an iPhone running iOS 17.1. This problem seems to be specific to this iOS version, as I did not observe similar issues on earlier versions.
### Steps to Reproduce
1. Integrate `mapbox-maps-flutter` into a Flutter application.
2. Run the application on an iPhone with iOS 17.1.
3. Observe the application's memory usage over time.
### Expected Behavior
The memory usage should remain stable over time when the map is displayed.
### Actual Behavior
The memory usage consistently increases, indicating a potential memory leak.
### Additional Information
- This issue is reproducible in both debug and release modes.
- No such issue was observed on devices running earlier versions of iOS.
Please look into this matter, as it affects the performance and reliability of applications using `mapbox-maps-flutter` on the latest iOS version. Thank you!
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 the issue in a Flutter application on an iPhone running iOS 17.1, comparing memory usage in debug and release modes with earlier iOS versions. Done means the map display no longer shows steadily increasing memory usage under the reported conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter, ios
- Domain
- mobile, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100