Probable Memory Leak about android-preferencesmanager

[SimonMarquis]

I don't see any issue here. ViewHolders are retained since Activity doesn't seem to be destroyed in the usecase you're describing.
Are these objects retained after you quit the app with the back button?

[Robigus92]

I have developed an automated Memory Leak detection tool which test Activities executing different lifecycle events (rotations, background-foreground, dialog pop-up events) then forcing an ending Garbage Collection.

The idea is that if the activity lifecycles are well managed there should not be an increase of the used heap memory.

In AppListActivity, forcing the BF (Background-Foreground) events, it seems to be an increasing trend of those TextView. It means that BF events cause an increase of TextView objects in heap memory.

The designed Background-Foreground event works switching from an activity to another, involving the Activity's onStart-onStop lifecycle.

[SimonMarquis]

Android-PreferencesManager/PreferencesManager/src/main/java/fr/simon/marquis/preferencesmanager/ui/AppListActivity.java

Line 147 in 5c955ab

mAdapter = new AppAdapter(this, apps, emptyView);

Unfortunately the Adapter is always re-created (instead of updating it's internal data), that's the reason why you see doubled instances of ViewHolders.
But since I don't think the Adapter instance is retained anywhere except in the Activity, it won't be a memory leak.
Maybe you have more details about the retained cycles of these objects?

[Robigus92]

Have you considered to use a Loader instead of managing the listView through AsyncTask?
Loaders should manage lifecycles automatically, avoiding such problems.

https://developer.android.com/guide/components/loaders.html

[SimonMarquis]

Unfortunately this project is no longer maintained and I don't have enough time to invest in this right now.