[DO NOT MERGE] Sharing a repro scenario for a leak related to Recomposer.snapshotInvalidations #1409
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.
I'm opening this just as a demo, I'll close the PR immediately after, this isn't meant to be merged.
The core of the issue is that large object graphs can be retained by
Recomposer.snapshotInvalidations
until the next recomposition. When an activity gets destroyed, there's no more recomposition there, soRecomposer.snapshotInvalidations
isn't cleared until something else needs recomposing. This is a problem in Compose tests where the Recomposer is a shared instance and a singleton.This issue has been impacting our UI tests more and more as we migrated to Compose, it's been 2 years now, and we've had to progressively disable leak detection in more and more tests as this kept firing and making tests fail. I only finally figured it out.
While there seems to be a workaround (composeTestRule.waitForIdle()), ideally we wouldn't need to do this.
I'll check in with folks if this is worth filing.
Here's what the failure looks like: