Android Drawables memory leak

Question

I work with several large drawables and I don\'t know how to manage memory leaks. I tracked the heap size of my application and it doesn\'t stop to grow (as the allocated me

Answer 1

The question seems answered but a post by Romain Guy seems relevant to get more info: Avoiding Memory Leaks.

Apparently, if you (for example) set a drawable as a background image to a text view by using setBackgroundDrawable* (thus attaching the drawable to the view) then change the orientation (destroying the Activity and redrawing the UI) the drawable will still have access to the old activity (after the old activity's destruction), thus creating a memory leak.

*(as a side note - setBackgroundDrawable has been deprecated since API level 16)

Answer 2

A memory leak happens when Java finds objects in the memory that are referenced by your code which is preventing the Garbage Collector from freeing this memory. A common cause in Android is referencing the Activity context rather than the Application context. Make sure your context references the Application (i.e. use getApplicationContext rather than using this. Check this video for explanation on Memory leaks and also check this question.