ansaurus

Question

Android: out of memory exception in Gallery

Answer 1

A:

The image you are loading in gallery 5 or 6 could be too large to load and it is exceeding the maximum size allow by the VM.

Ryan Conrad 2010-07-13 14:58:32

which is usually 16Mb.

Pentium10 2010-07-13 15:02:41

Hi Ryan. Gallery 1 is largest in size and it loads. Also, it is not a specific gallery that crashes. It is the number of galleries I already went through that matters. Btw, each gallery is between 2.8 MB and 4.4 MB.

Rob 2010-07-13 15:13:57

Its not necessarily the size of the gallery, its the size of the image, unless you are "preloading" all the images.

Ryan Conrad 2010-07-13 15:31:05

> "which is usually 16Mb": For devices with lower display resolution (usually older models) it's 16 MB, like G1, for devices like Nexus One, HTC Desire the limit is at 24MB, while for the Samsung Galaxy S, it's even higher at 48 MB already. (max heap per app)

Mathias Lin 2010-07-13 15:38:52

@Ryan - I fetch all the images from the Web, place them in an arrayList of Drawables and only then proceed to load the activity which holds the gallery. Btw, is there a limit on a single image??

Rob 2010-07-13 15:39:25

you preloading all the images is probably the problem. I tried something like that on one of the apps i was writing and if I preloaded all the images in drawables, that is when I would run in to the out of memory exception.

Ryan Conrad 2010-07-14 02:14:13

Answer 2

+1 A:

The images are fetched from the Web, each ranging from 300K to 500K in size, and stored in an arrayList of Drawables.

The kb file size of the image you're loading from the web isn't directly relevant. Since they're converted into bitmaps you need to calculate width * height * 4 bytes per image for regular ARGB images. (width and height in px).

The bitmaps consume native heap, which usually doesn't show in a hprof. The hprof should only show you the number of objects, i.e. BitmapDrawables or Bitmaps that are left.

I use this code in my app to output the current used memory used by the app and native heap:

public static void logHeap(Class clazz) {
    Double allocated = new Double(Debug.getNativeHeapAllocatedSize())/new Double((1048576));
    Double available = new Double(Debug.getNativeHeapSize())/1048576.0);
    Double free = new Double(Debug.getNativeHeapFreeSize())/1048576.0);
    DecimalFormat df = new DecimalFormat();
    df.setMaximumFractionDigits(2);
    df.setMinimumFractionDigits(2);

    Log.d(APP, "debug. =================================");
    Log.d(APP, "debug.heap native: allocated " + df.format(allocated) + "MB of " + df.format(available) + "MB (" + df.format(free) + "MB free) in [" + clazz.getName().replaceAll("com.myapp.android.","") + "]");
    Log.d(APP, "debug.memory: allocated: " + df.format(new Double(Runtime.getRuntime().totalMemory()/1048576)) + "MB of " + df.format(new Double(Runtime.getRuntime().maxMemory()/1048576))+ "MB (" + df.format(new Double(Runtime.getRuntime().freeMemory()/1048576)) +"MB free)");
    System.gc();
    System.gc();

    // don't need to add the following lines, it's just an app specific handling in my app        
    if (allocated>=(new Double(Runtime.getRuntime().maxMemory())/new Double((1048576))-MEMORY_BUFFER_LIMIT_FOR_RESTART)) {
        android.os.Process.killProcess(android.os.Process.myPid());
    }
}

which I call when starting or finishing an activity during development.

logHeap(this.getClass());

Here are some informative links - generally there are lots of threads about this topic on here.

http://stackoverflow.com/questions/1945142/bitmaps-in-android http://stackoverflow.com/questions/2203806/android-eclipse-mat-does-not-appear-to-show-all-my-apps-objects

Here's also a useful slide by Romain Guy (Android Framework engineer) about soft references, weak references, simple caches, image handling: http://docs.huihoo.com/google/io/2009/Th_0230_TurboChargeYourUI-HowtomakeyourAndroidUIfastandefficient.pdf

Mathias Lin 2010-07-13 15:54:54

Mathias, thanks a lot. I will give it a try

Rob 2010-07-14 06:13:00

Mathias, I edited the question with some output using your function. what do you make of this? Thanks

Rob 2010-07-14 08:59:20

After carefully examining the heapLog output I realized that something is not cleared properly. I thought that setCallBack(null) and nulling the element would suffice, but only after applying recycle() the memory cleared. Thanks, Mathias.

Rob 2010-07-15 06:14:18

Hi Rob, I also had recycle() in mind but not for your case/code since you used BitmapDrawables and not Bitmaps itself. Therefore interested, which objects did you call the recyle() upon in the end?

Mathias Lin 2010-07-15 15:15:24

Hi Mathais. I called BitmapDrawable's getBitmap() to get the bitmap and applied recycle() on it.

Rob 2010-07-18 13:13:32

Answer 3

A:

Here are some advices:

Do you use inSampleSize option? It reduces memory consumption if you scale images. http://stackoverflow.com/questions/477572/android-strange-out-of-memory-issue/823966#823966
You should call Bitmap.recycle() when you don't need images any more. I think it's important in your case. http://stackoverflow.com/questions/3037027/android-outofmemoryerror-bitmap-size-exceeds-vm-budget-with-no-reason-i-can-see/3184850#3184850

Fedor 2010-07-14 13:19:02

Thanks Fedor. After examining the output of Mathias' logHeap function I realized that something is not getting cleared. I applied recycle() and the memory was freed. With your permission, I will credit Mathias with the answer.

Rob 2010-07-15 06:17:10

No problem :-))

Fedor 2010-07-15 07:34:09

ansaurus

tags:

views:

answers:

Android: out of memory exception in Gallery

related questions