serious memory leak in iOS platform
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 7.9k
- Forks
- 914
- PR merge metrics
- No merged PRs in 30d
Description
On iOS, we can't call the detachChild method properly when we swipe to close the page, which causes a serious memory leak, is there any way to solve this problem
Sent from PPHub
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 locating the iOS implementation of detachChild and reproduce the leak by swiping to close a page. Trace why detachChild is not called properly during that flow. Done means the child is detached when the page closes and the reported memory leak no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100