worldclockwidget
worldclockwidget copied to clipboard
Memory Leak
After a double rotation of the AddClockActivity there are in heap memory 2 instances more of:
class ch.corten.aha.worldclock.AddClockActivity @ 0x12cbd800 class ch.corten.aha.worldclock.AddClockActivity$TimeZoneListFragment @ 0x12cc7c00
It should not be like this because the rotation events 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.
Hi @robigus I will look into it. Sorry I am traveling at the moment.