You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 16, 2021. It is now read-only.
user goes back from fragment B -> A, but C presenter retained in memory.
It happens many times and creates serious memory footprint. After 20 times or so the app may even freeze.
Basically when there is a check in onDestroy()isFragmentInBackstack() = false, but isFragmentRemoving() = false in nested fragment and nothing get cleared
How to free presenter manually in such case?
The text was updated successfully, but these errors were encountered:
Can you explain what is causing the memory leak or churn? Are you saying multiple C presenters are being created? Is the B destroyed at the right time but not the C presenter?
StefMa
changed the title
How to free presenter manually?
How to free presenter manually / Issue with nested fragments
Sep 29, 2017
StefMa
changed the title
How to free presenter manually / Issue with nested fragments
How to free presenter manually / Nested fragments don't get destroyed
Sep 29, 2017
StefMa
changed the title
How to free presenter manually / Nested fragments don't get destroyed
How to free presenter manually / Nested fragments/presenter don't get destroyed
Sep 29, 2017
I have a situation when user switch fragments
It happens many times and creates serious memory footprint. After 20 times or so the app may even freeze.
Basically when there is a check in
onDestroy()
isFragmentInBackstack() = false
, butisFragmentRemoving() = false
in nested fragment and nothing get clearedHow to free presenter manually in such case?
The text was updated successfully, but these errors were encountered: