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
during watching subathon VOD, what about 20 Hours or even 40 Hours go, I encounter some memory leaks. One time it was so massive, that the complete phone got very slow and later on it killed the whole twire app.
I decided to see if I can find those memory leaks with Android Profiler and it seems i found them. I even was capable to fix them.
I hope those fixes can be flow in, in the next official version.
Here some detail:
one fix is that there was used a weak reference of the an activity in a background task, but the activity was given in the doBackground function and that still causes a memory leak .. it should be given in the constructor of the background task class.
the other fixes are related to static functions what got excluded by garbage collection, Especially by static Fragment classes.
The text was updated successfully, but these errors were encountered:
Hi,
during watching subathon VOD, what about 20 Hours or even 40 Hours go, I encounter some memory leaks. One time it was so massive, that the complete phone got very slow and later on it killed the whole twire app.
I decided to see if I can find those memory leaks with Android Profiler and it seems i found them. I even was capable to fix them.
Here are my fixes: (.diff files)
MemoryLeakFix.zip
I hope those fixes can be flow in, in the next official version.
Here some detail:
one fix is that there was used a weak reference of the an activity in a background task, but the activity was given in the doBackground function and that still causes a memory leak .. it should be given in the constructor of the background task class.
the other fixes are related to static functions what got excluded by garbage collection, Especially by static Fragment classes.
The text was updated successfully, but these errors were encountered: