QuantumBadger / QuantumBadger/RedReader
resource leaks?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 527
- Avg merge
- 20d 10h
- Merged PRs (30d)
- 3
Description
Android 11, RedReader v1.24.1，google pixel
I repeated the following sequence in the following interface: When I returned to the main interface of the device and then returned to the application, I found that the Proxy Binders of the application were constantly rising, and I suspected that there were resource leaks related to Proxy Binders in the current interface life cycle.
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
Start by reproducing the reported sequence on Android 11 with RedReader v1.24.1 on a Google Pixel, then observe whether Proxy Binder counts continue rising as the app leaves and re-enters the foreground. Done means identifying and resolving the lifecycle-related resource leak so repeated transitions no longer cause the count to grow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100