Home/ Questions/Q 8920565
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T06:18:17+00:00

I experience some memory leaks in my android application. I’ve already used MAT to

  • 0

I experience some memory leaks in my android application. I’ve already used MAT to analyze the memory usage. But I have one question from the DDMS perspectiv in Eclipse, what does 1-byte array[byte[], boolean[]) mean?

enter image description here

Is this specific for my application? You can see that this is the big memory leak issue, this always increases in size, and the rest will increase and decrease randomly. My guess is that the GC doesn’t catch this type. Can anybody explain why this happen, with this little information?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A byte and a boolean are each 1 byte. If you have an array of those you have a “1-byte array”.

    A ByteBuffer for example should internally hold one of those.

    You have a total of 614 of them where the smallest one be a byte[24] (or boolean[24]), the largest one is 3MB. All of them together use 104MB.

    The GC will get rid of them if they are no longer referenced.

    For example when you put

    private static byte myArray[] = new byte[3 * 1024 * 1024];

    in one of your classes and never set it back to null (myArray = null) then this one can’t be garbage collected because another Object has a reference to it. The object would be the class itself (as in String.class). The class object can’t be garbage collected since classes are never unloaded. (they are referenced by their ClassLoader which could itself be referenced / loaded by another ClassLoader and you can’t create Objects & use classes without them – they need to stay and they need to keep a reference to their classes)

    It’s usually not that simple but often start with static somewhere.

    Within MAT (after you force GC) look at the reference chain for the objects that are no longer intended to stay alive and identify the one Object that holds the reference. Set that one to null in your code and your leak is gone. Explained in more detail here:

    http://android-developers.blogspot.de/2011/03/memory-analysis-for-android.html

    • 0