Fix GC Root bugs that missed leaks #1168
Merged
Conversation
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
In Perflib, Snapshot.getGcRoots() only returns the GC roots from the first heap. Based on empirical evidence, it seems like Android has 4 heaps, and the GC Roots used to only be in the first heap, but more recent versions of Android have GC Roots in other heaps as well. This means LeakCanary would sometimes show "No Leak Found" when there actually was a leak. Fixes #1163
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.
In Perflib, Snapshot.getGcRoots() only returns the GC roots from the first heap. Based on empirical evidence, it seems like Android has 4 heaps, and the GC Roots used to only be in the first heap, but more recent versions of Android have GC Roots in other heaps as well.
This means LeakCanary would sometimes show "No Leak Found" when there actually was a leak.
Fixes #1163