7

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 memory).

It is especially the "byte array (byte[])" type which grows up and never decrease. (in the DDMS Heap view on Eclipse)

My application is composed of one activity which uses fragments. Those fragments are displaying several large images. I tried to set drawables callback to null, set drawables to null, clear my volatile cache (which prevent my app from doing too many disk IO) when I pop back a fragment but the heap never decrease.

In fact, each time I call : Drawable.createFromResourceStream(context.getResources(), value, new FileInputStream(f), f.getName(), opts); the heap grows up. How can I free memory ?

Thanks !

abecker
  • 885
  • 1
  • 10
  • 15

2 Answers2

6

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.

Community
  • 1
  • 1
Mohamed_AbdAllah
  • 5,311
  • 3
  • 28
  • 47
  • I reference the Application Context and not the Activity Context, you think the issue is that my fragments are never destroyed and they leak ? – abecker Sep 15 '12 at 14:57
  • Maybe, check the video in my answer to how to use the SDK memory analysis tool (MAT) to find the objects that are leaking – Mohamed_AbdAllah Sep 15 '12 at 15:00
  • 1
    Hey ! I solved my issue ! In fact, my fragments were kept in memory and it was my static volatile cache that kept it. I don't really know why it has this behaviour. I instanced one DrawableManager, when I create a fragment ,which have several method to retrieve Drawables from disk or by networking. When it delivers one to my views, it was keeping it in a static HashMap (in order to reuse this cache in my others fragments). I just make my HashMap none static (can't reuse volatile cache between fragments). I don't know why my fragment was kept in memory. – abecker Sep 15 '12 at 16:15
3

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)

Community
  • 1
  • 1
studiou
  • 301
  • 3
  • 6