fix(android): Memory leak from lifecycleObserver mapView reference#98
Merged
pinpong merged 1 commit intopinpong:devfrom Feb 1, 2026
Merged
fix(android): Memory leak from lifecycleObserver mapView reference#98pinpong merged 1 commit intopinpong:devfrom
pinpong merged 1 commit intopinpong:devfrom
Conversation
Owner
|
@ottor-o thanks for your contribution. |
ottor-o
changed the title
ottor-o
changed the title
|
🎉 This PR is included in version 1.11.1-dev.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull request
Please ensure this PR targets the
devbranch and follows the project conventions.CI already runs linting, formatting, and build checks automatically.
Before submitting
devbranch (notmain)Summary
Fixes a memory leak caused by mapView reference kept by lifecycleObserver
Type of change
Scope
Additional notes
There's a memory leak caused by lifecycleObserver apparently because if keeps a reference of mapView. Nullifying lifecycleObserver fixed it for me.
The memory leak can be observed by putting GoogleMapsView on a stack or a modal and then closing and navigating to it multiple times. The easiest way to reproduce it is to render GoogleMapsView on a flatlist a few hundred times and to scroll back and forth causing an out of memory crash.