[Compose Sample] Flipper Ribtree Plugin produces an Interactor Memory Leak
Open
Nobody has claimed this yet.
Android
- Dominant language
- Kotlin
- Stars
- 7.9k
- Forks
- 914
- PR merge metrics
- No merged PRs in 30d
Description
Build and run the Compose sample with Leak Canary integrated and it'll notify interactors leak due to the Rib Plugin for Flipper.
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
Build and run the Compose sample with LeakCanary enabled, then inspect the Rib Plugin for Flipper and the reported interactor leak. Done means the sample no longer reports interactor leaks caused by the Flipper Rib Plugin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100