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 May 20, 2019. It is now read-only.
After a double rotation of the CleanerActivity there are in heap memory 2 instances more of:
class com.frozendevs.cache.cleaner.activity.CleanerActivity @ 0x12caf000
class com.frozendevs.cache.cleaner.fragment.CleanerFragment$3 @ 0x12d45100
class com.frozendevs.cache.cleaner.fragment.CleanerFragment$4 @ 0x12d451c0
It should not be like this because the rotations return to the same GUI state and the memory should stay in the same state as well. It could be a symptom of a bad management of the onCreate-onDestroy lifecycle.
I have encountered this problem on an Android emulator running 7.1.1 os version.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After a double rotation of the CleanerActivity there are in heap memory 2 instances more of:
class com.frozendevs.cache.cleaner.activity.CleanerActivity @ 0x12caf000
class com.frozendevs.cache.cleaner.fragment.CleanerFragment$3 @ 0x12d45100
class com.frozendevs.cache.cleaner.fragment.CleanerFragment$4 @ 0x12d451c0
It should not be like this because the rotations return to the same GUI state and the memory should stay in the same state as well. It could be a symptom of a bad management of the onCreate-onDestroy lifecycle.
I have encountered this problem on an Android emulator running 7.1.1 os version.
The text was updated successfully, but these errors were encountered: