Explicitly null map reference from renderer#687
Merged
Conversation
ffe9c3c to
ca10b56
Compare
ca10b56 to
245a11c
Compare
alexander-kulikovskii
approved these changes
Sep 30, 2021
axti
approved these changes
Sep 30, 2021
pengdev
approved these changes
Sep 30, 2021
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
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.
PRs must be submitted under the terms of our Contributor License Agreement CLA.
Fixes: < Link to related issues that will be fixed by this pull request, if they exist >
Pull request checklist:
@JvmOverloads,@file:JvmName, etc).mapbox-maps-androidchangelog:<changelog>Fix native memory leak by explicitly nulling map reference from renderer.</changelog>.Summary of changes
Fix native memory leak by explicitly nulling map reference from renderer.
Additionally refactor code a bit by making
MapControllermore responsible for storing main strong link toMapInterface.Memory consumption looks now after the fix
User impact (optional)