> The following situation happens only in a few cases, but it does more
> than once.
> ---------------------------------

> I'm receiving several OutOfMemoryError in
> BitmapFactory.nativeDecodeByteArray.

> DDMS-Heap-View never broke the 16MB barrier. I can't even get it above
> 6MB, while going wild and smashing keys like a monkey:
> -----------------------------------
> 1       5,820 MB        2,751 MB        3,069 MB        47,26%  54.433
> -----------------------------------

> The situation is that I have a ThreadPoolExector:
> -----------------------------------
> protected ExecutorService mThreadPool = Executors.newCachedThreadPool
> ();
> -----------------------------------
> ... ,which load several 256x256 pngs to the RAM. (Average png-size: <
> 20kb)

> StackTrace-Desciption:
> That OutOfMemoryError happens several times in the Threads, until the
> VM decides its enough and stops the whole process.

> StackTrace:
> #################################
> W/AudioFlinger(   24): write blocked for 49 msecs
> W/AudioFlinger(   24): write blocked for 48 msecs
> W/AudioFlinger(   24): write blocked for 49 msecs
> D/dalvikvm(  410): GC freed 31478 objects / 1613104 bytes in 196ms
> D/dalvikvm(  410): GC freed 6404 objects / 991024 bytes in 151ms
> D/dalvikvm(  410): GC freed 5224 objects / 1229888 bytes in 137ms
> E/SOCKETLOG(  410): add_recv_stats recv 0
> E/SOCKETLOG(  410): add_recv_stats recv 0
> E/SOCKETLOG(  410): add_recv_stats recv 0
> E/SOCKETLOG(  410): add_recv_stats recv 0
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> E/        (  410): VM won't let us allocate 65536 bytes
> W/dalvikvm(  410): threadid=59: thread exiting with uncaught exception
> (group=0x40010e28)
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-6
> exiting due to uncaught exception
> E/        (  410): VM won't let us allocate 65536 bytes
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> W/dalvikvm(  410): threadid=65: thread exiting with uncaught exception
> (group=0x40010e28)
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> E/        (  410): VM won't let us allocate 65536 bytes
> W/dalvikvm(  410): threadid=43: thread exiting with uncaught exception
> (group=0x40010e28)
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-3
> exiting due to uncaught exception
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run
> (OSMMapTileFilesystemCache.java:234)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:648)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:673)
> E/AndroidRuntime(  410):        at java.lang.Thread.run(Thread.java:
> 935)
> E/        (  410): VM won't let us allocate 65536 bytes
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-9
> exiting due to uncaught exception
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> E/        (  410): VM won't let us allocate 65536 bytes
> W/dalvikvm(  410): threadid=61: thread exiting with uncaught exception
> (group=0x40010e28)
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run
> (OSMMapTileFilesystemCache.java:234)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:648)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:673)
> E/AndroidRuntime(  410):        at java.lang.Thread.run(Thread.java:
> 935)
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run
> (OSMMapTileFilesystemCache.java:234)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:648)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:673)
> E/AndroidRuntime(  410):        at java.lang.Thread.run(Thread.java:
> 935)
> E/        (  410): VM won't let us allocate 65536 bytes
> I/Process (   50): Sending signal. PID: 410 SIG: 3
> I/dalvikvm(  410): threadid=7: reacting to signal 3
> I/dalvikvm(  410): Wrote stack trace to '/data/anr/traces.txt'
> W/dalvikvm(  410): threadid=73: thread exiting with uncaught exception
> (group=0x40010e28)
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-10
> exiting due to uncaught exception
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run
> (OSMMapTileFilesystemCache.java:234)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:648)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:673)
> E/AndroidRuntime(  410):        at java.lang.Thread.run(Thread.java:
> 935)
> I/Process (   50): Sending signal. PID: 410 SIG: 3
> W/ActivityManager(   50): Process org.andnav2 has crashed too many
> times: killing!
> D/ActivityManager(   50):   Force finishing activity
> org.andnav2/.ui.map.OpenStreetDDMap
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-7
> exiting due to uncaught exception
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run
> (OSMMapTileFilesystemCache.java:234)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:648)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:673)
> E/AndroidRuntime(  410):        at java.lang.Thread.run(Thread.java:
> 935)
> W/dalvikvm(  410): threadid=63: thread exiting with uncaught exception
> (group=0x40010e28)
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-8
> exiting due to uncaught exception
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run
> (OSMMapTileFilesystemCache.java:234)
> E/AndroidRuntime(  410):        at

> The following situation happens only in a few cases, but it does more
> than once.
> ---------------------------------

> I'm receiving several OutOfMemoryError in
> BitmapFactory.nativeDecodeByteArray.

> DDMS-Heap-View never broke the 16MB barrier. I can't even get it above
> 6MB, while going wild and smashing keys like a monkey:
> -----------------------------------
> 1       5,820 MB        2,751 MB        3,069 MB        47,26%  54.433
> -----------------------------------

> The situation is that I have a ThreadPoolExector:
> -----------------------------------
> protected ExecutorService mThreadPool = Executors.newCachedThreadPool
> ();
> -----------------------------------
> ... ,which load several 256x256 pngs to the RAM. (Average png-size: <
> 20kb)

> StackTrace-Desciption:
> That OutOfMemoryError happens several times in the Threads, until the
> VM decides its enough and stops the whole process.

> StackTrace:
> #################################
> W/AudioFlinger(   24): write blocked for 49 msecs
> W/AudioFlinger(   24): write blocked for 48 msecs
> W/AudioFlinger(   24): write blocked for 49 msecs
> D/dalvikvm(  410): GC freed 31478 objects / 1613104 bytes in 196ms
> D/dalvikvm(  410): GC freed 6404 objects / 991024 bytes in 151ms
> D/dalvikvm(  410): GC freed 5224 objects / 1229888 bytes in 137ms
> E/SOCKETLOG(  410): add_recv_stats recv 0
> E/SOCKETLOG(  410): add_recv_stats recv 0
> E/SOCKETLOG(  410): add_recv_stats recv 0
> E/SOCKETLOG(  410): add_recv_stats recv 0
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> E/        (  410): VM won't let us allocate 65536 bytes
> W/dalvikvm(  410): threadid=59: thread exiting with uncaught exception
> (group=0x40010e28)
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-6
> exiting due to uncaught exception
> E/        (  410): VM won't let us allocate 65536 bytes
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> W/dalvikvm(  410): threadid=65: thread exiting with uncaught exception
> (group=0x40010e28)
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> E/        (  410): VM won't let us allocate 65536 bytes
> W/dalvikvm(  410): threadid=43: thread exiting with uncaught exception
> (group=0x40010e28)
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-3
> exiting due to uncaught exception
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run
> (OSMMapTileFilesystemCache.java:234)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:648)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:673)
> E/AndroidRuntime(  410):        at java.lang.Thread.run(Thread.java:
> 935)
> E/        (  410): VM won't let us allocate 65536 bytes
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-9
> exiting due to uncaught exception
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> E/        (  410): VM won't let us allocate 65536 bytes
> W/dalvikvm(  410): threadid=61: thread exiting with uncaught exception
> (group=0x40010e28)
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run
> (OSMMapTileFilesystemCache.java:234)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:648)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:673)
> E/AndroidRuntime(  410):        at java.lang.Thread.run(Thread.java:
> 935)
> E/dalvikvm-heap(  410): 65536-byte external allocation too large for
> this process.
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run
> (OSMMapTileFilesystemCache.java:234)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:648)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:673)
> E/AndroidRuntime(  410):        at java.lang.Thread.run(Thread.java:
> 935)
> E/        (  410): VM won't let us allocate 65536 bytes
> I/Process (   50): Sending signal. PID: 410 SIG: 3
> I/dalvikvm(  410): threadid=7: reacting to signal 3
> I/dalvikvm(  410): Wrote stack trace to '/data/anr/traces.txt'
> W/dalvikvm(  410): threadid=73: thread exiting with uncaught exception
> (group=0x40010e28)
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-10
> exiting due to uncaught exception
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run
> (OSMMapTileFilesystemCache.java:234)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:648)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:673)
> E/AndroidRuntime(  410):        at java.lang.Thread.run(Thread.java:
> 935)
> I/Process (   50): Sending signal. PID: 410 SIG: 3
> W/ActivityManager(   50): Process org.andnav2 has crashed too many
> times: killing!
> D/ActivityManager(   50):   Force finishing activity
> org.andnav2/.ui.map.OpenStreetDDMap
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-7
> exiting due to uncaught exception
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run
> (OSMMapTileFilesystemCache.java:234)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:648)
> E/AndroidRuntime(  410):        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:673)
> E/AndroidRuntime(  410):        at java.lang.Thread.run(Thread.java:
> 935)
> W/dalvikvm(  410): threadid=63: thread exiting with uncaught exception
> (group=0x40010e28)
> E/AndroidRuntime(  410): Uncaught handler: thread pool-8-thread-8
> exiting due to uncaught exception
> E/AndroidRuntime(  410): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime(  410):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime(  410):        at
> org.andnav2.osm.views.tiles.OSMMapTileFilesystemCache$1.run

>  I've run into this exact same problem a number of times myself. Not
> sure if its a bug or just a limitation of the jvm, can't seem to
> process more than a few large bitmaps without this occuring, this
> always seems to occur when decoding bitmaps from file.

> >  I've run into this exact same problem a number of times myself. Not
> > sure if its a bug or just a limitation of the jvm, can't seem to
> > process more than a few large bitmaps without this occuring, this
> > always seems to occur when decoding bitmaps from file.

> Neither, you are just using too much memory.

> --
> Romain Guy
> Android framework engineer
> romain...@android.com

> Note: please don't send private questions to me, as I don't have time
> to provide private support.  All such questions should be posted on
> public forums, where I and others can see and answer them

On Tue, Dec 16, 2008 at 7:34 AM, Mark K <mark.ka...@gmail.com> wrote:

>  Is there a work around for this problem? Something I need to do
> differently perhaps? It seems like garbage collection is not occurring
> between successive bitmap decoding operations. Explicitly calling gc()
> does not seem to help. This is particularly a problem on the G1,
> because there is no way to reduce the camera resolution, all of the
> camera pictures are large. If I loop through a directory of pictures
> taken by the camera and use BitmapFactory.decodeFile(), I will get an
> out of memory error on the 2nd or 3rd iteration. Since I am only
> displaying/decoding one bitmap at a time I would hope that garbage
> collection would free up the memory between operations such that this
> does not occur. Any help would be greatly appreciated. Here's the code
> I use: This code runs a slide show of the images in the camera
> directory, it uses Handler.postDelayed() to render each picture. Is
> there anyway to tweak the code to get rid of the out of memory
> problem.

> public boolean slideShow()
>    {
>        String baseDir = "/sdcard/dcim/Camera/";
>        long showTime = 1500;

>        File dir = new File(baseDir);
>        File[] pics = dir.listFiles();
>        for ( int i=0; i<pics.length; i++ )
>        {
>                String pic=baseDir+pics[i].getName();
>                handler.postDelayed(new ShowSlide(pic), i*showTime);
>        }
>        return true;
>    }

> class ShowSlide extends Thread
>    {
>        String pc="";
>        public ShowSlide(String pc)
>        {
>                this.pc=pc;
>        }
>        public void run()
>        {
>                System.out.println("Showing picture: "+pc.toString());
>                displayPicture(pc);
>        }
>    }

> public boolean displayPicture(String filepath)
>    {
>               File file = new File(filepath);
>                BitmapFactory bfac = new BitmapFactory();
>        try
>        {
>                bm = bfac.decodeFile(filepath);// out of memory error occurs
> here!
>                handler.post(new SetImage(iView, bm));
>        }
>        catch(Exception e)
>        {
>           Log.e(TAG,"display picture failed: "+filepath+" "+e.toString
> ());
>           e.printStackTrace();
>           return false;
>        }

>        return true;
>    }

> class SetImage extends Thread
>    {
>        ImageView vv;
>        Bitmap bb;
>        public SetImage(ImageView vv, Bitmap bb)
>        {
>                this.vv=vv;
>                this.bb=bb;
>        }
>        public void run()
>        {
>                vv.setImageBitmap(bb);
>         }
>    }

> On Dec 15, 2:48 pm, Romain Guy <romain...@google.com> wrote:
> > >  I've run into this exact same problem a number of times myself. Not
> > > sure if its a bug or just a limitation of the jvm, can't seem to
> > > process more than a few large bitmaps without this occuring, this
> > > always seems to occur when decoding bitmaps from file.

> > Neither, you are just using too much memory.

> > --
> > Romain Guy
> > Android framework engineer
> > romain...@android.com

> > Note: please don't send private questions to me, as I don't have time
> > to provide private support.  All such questions should be posted on
> > public forums, where I and others can see and answer them

> I too ran into this many times and my images are not on the disk they are
> fetched from the network moreover none of my images exceed 5kb so i don't
> understand why is it even trying to allocate 74752bytes.

}

>>  I've run into this exact same problem a number of times myself. Not
>> sure if its a bug or just a limitation of the jvm, can't seem to
>> process more than a few large bitmaps without this occuring, this
>> always seems to occur when decoding bitmaps from file.

> Neither, you are just using too much memory.

> --
> Romain Guy
> Android framework engineer
> romain...@android.com

> Note: please don't send private questions to me, as I don't have time
> to provide private support.  All such questions should be posted on
> public forums, where I and others can see and answer them

> Its a little raw, but if you know you're absolutely done using a given  
> bitmap object, you can call bitmap.recycle(). This immediately frees  
> up the memory associated with the bitmap, and marks it as "dead",  
> meaning it cannot be referenced again (i.e. don't try to draw or get/
> set its pixels anymore).

> i.e.

> for (all of my big images) {
>      Bitmap b = decode(...);
>      canvas.drawBitmap(b, ...);
>      b.recycle();
>      // yikes, don't reference b again)

> }

> On Dec 15, 2008, at 9:04 PM, Mark K wrote:

>   Is there a work around for this problem? Something I need to do
> differently perhaps? It seems like garbage collection is not occurring
> between successive bitmap decoding operations. Explicitly calling gc()
> does not seem to help. This is particularly a problem on the G1,
> because there is no way to reduce the camera resolution, all of the
> camera pictures are large. If I loop through a directory of pictures
> taken by the camera and use BitmapFactory.decodeFile(), I will get an
> out of memory error on the 2nd or 3rd iteration. Since I am only
> displaying/decoding one bitmap at a time I would hope that garbage
> collection would free up the memory between operations such that this
> does not occur. Any help would be greatly appreciated. Here's the code
> I use: This code runs a slide show of the images in the camera
> directory, it uses Handler.postDelayed() to render each picture. Is
> there anyway to tweak the code to get rid of the out of memory
> problem.

> public boolean slideShow()
>     {
>         String baseDir = "/sdcard/dcim/Camera/";
>         long showTime = 1500;

>         File dir = new File(baseDir);
>         File[] pics = dir.listFiles();
>         for ( int i=0; i<pics.length; i++ )
>         {
>                 String pic=baseDir+pics[i].getName();
>                 handler.postDelayed(new ShowSlide(pic), i*showTime);
>         }
>         return true;
>     }

> class ShowSlide extends Thread
>     {
>         String pc="";
>         public ShowSlide(String pc)
>         {
>                 this.pc=pc;
>         }
>         public void run()
>         {
>                 System.out.println("Showing picture: "+pc.toString());
>                 displayPicture(pc);
>         }
>     }

> public boolean displayPicture(String filepath)
>     {
>                File file = new File(filepath);
>                 BitmapFactory bfac = new BitmapFactory();
>         try
>         {
>                 bm = bfac.decodeFile(filepath);// out of memory error occurs
> here!
>                 handler.post(new SetImage(iView, bm));
>         }
>         catch(Exception e)
>         {
>            Log.e(TAG,"display picture failed: "+filepath+" "+e.toString
> ());
>            e.printStackTrace();
>            return false;
>         }

>         return true;
>     }

> class SetImage extends Thread
>     {
>         ImageView vv;
>         Bitmap bb;
>         public SetImage(ImageView vv, Bitmap bb)
>         {
>                 this.vv=vv;
>                 this.bb=bb;
>         }
>         public void run()
>         {
>                 vv.setImageBitmap(bb);
>         }
>     }

> On Dec 15, 2:48 pm, Romain Guy <romain...@google.com> wrote:

> >>  I've run into this exact same problem a number of times myself. Not
> >> sure if its a bug or just a limitation of the jvm, can't seem to
> >> process more than a few large bitmaps without this occuring, this
> >> always seems to occur when decoding bitmaps from file.

> > Neither, you are just using too much memory.

> > --
> > Romain Guy
> > Android framework engineer
> > romain...@android.com

> > Note: please don't send private questions to me, as I don't have time
> > to provide private support.  All such questions should be posted on
> > public forums, where I and others can see and answer them- Hide quoted text -

> - Show quoted text -

> Thanks for the beta on the bitmap,recycle(), it works! Before
> processing the next bitmap I use this code to free up memory. I have a
> class level Bitmap object.

>                                 Bitmap bm;// class level

>                                 if (bm!=null)
>                 {
>                          bm.recycle();
>                          try
>                          {
>                                 Thread.sleep(100);
>                          }
>                          catch(Exception e){}
>                          bm=null;
>                          System.gc();
>                          try
>                          {
>                                 Thread.sleep(100);
>                          }
>                          catch(Exception e){}
>                 }
>                                // create new bitmap and start again.

> Thanks again, it works!

> On Dec 17, 5:56 am, Mike Reed <r...@google.com> wrote:

> > Its a little raw, but if you know you're absolutely done using a given  
> > bitmap object, you can call bitmap.recycle(). This immediately frees  
> > up the memory associated with the bitmap, and marks it as "dead",  
> > meaning it cannot be referenced again (i.e. don't try to draw or get/
> > set its pixels anymore).

> > i.e.

> > for (all of my big images) {
> >      Bitmap b = decode(...);
> >      canvas.drawBitmap(b, ...);
> >      b.recycle();
> >      // yikes, don't reference b again)

> > }

> > On Dec 15, 2008, at 9:04 PM, Mark K wrote:

> >   Is there a work around for this problem? Something I need to do
> > differently perhaps? It seems like garbage collection is not occurring
> > between successive bitmap decoding operations. Explicitly calling gc()
> > does not seem to help. This is particularly a problem on the G1,
> > because there is no way to reduce the camera resolution, all of the
> > camera pictures are large. If I loop through a directory of pictures
> > taken by the camera and use BitmapFactory.decodeFile(), I will get an
> > out of memory error on the 2nd or 3rd iteration. Since I am only
> > displaying/decoding one bitmap at a time I would hope that garbage
> > collection would free up the memory between operations such that this
> > does not occur. Any help would be greatly appreciated. Here's the code
> > I use: This code runs a slide show of the images in the camera
> > directory, it uses Handler.postDelayed() to render each picture. Is
> > there anyway to tweak the code to get rid of the out of memory
> > problem.

> > public boolean slideShow()
> >     {
> >         String baseDir = "/sdcard/dcim/Camera/";
> >         long showTime = 1500;

> >         File dir = new File(baseDir);
> >         File[] pics = dir.listFiles();
> >         for ( int i=0; i<pics.length; i++ )
> >         {
> >                 String pic=baseDir+pics[i].getName();
> >                 handler.postDelayed(new ShowSlide(pic), i*showTime);
> >         }
> >         return true;
> >     }

> > class ShowSlide extends Thread
> >     {
> >         String pc="";
> >         public ShowSlide(String pc)
> >         {
> >                 this.pc=pc;
> >         }
> >         public void run()
> >         {
> >                 System.out.println("Showing picture: "+pc.toString());
> >                 displayPicture(pc);
> >         }
> >     }

> > public boolean displayPicture(String filepath)
> >     {
> >                File file = new File(filepath);
> >                 BitmapFactory bfac = new BitmapFactory();
> >         try
> >         {
> >                 bm = bfac.decodeFile(filepath);// out of memory error occurs
> > here!
> >                 handler.post(new SetImage(iView, bm));
> >         }
> >         catch(Exception e)
> >         {
> >            Log.e(TAG,"display picture failed: "+filepath+" "+e.toString
> > ());
> >            e.printStackTrace();
> >            return false;
> >         }

> >         return true;
> >     }

> > class SetImage extends Thread
> >     {
> >         ImageView vv;
> >         Bitmap bb;
> >         public SetImage(ImageView vv, Bitmap bb)
> >         {
> >                 this.vv=vv;
> >                 this.bb=bb;
> >         }
> >         public void run()
> >         {
> >                 vv.setImageBitmap(bb);
> >         }
> >     }

> > On Dec 15, 2:48 pm, Romain Guy <romain...@google.com> wrote:

> > >>  I've run into this exact same problem a number of times myself. Not
> > >> sure if its a bug or just a limitation of the jvm, can't seem to
> > >> process more than a few large bitmaps without this occuring, this
> > >> always seems to occur when decoding bitmaps from file.

> > > Neither, you are just using too much memory.

> > > --
> > > Romain Guy
> > > Android framework engineer
> > > romain...@android.com

> > > Note: please don't send private questions to me, as I don't have time
> > > to provide private support.  All such questions should be posted on
> > > public forums, where I and others can see and answer them- Hide quoted text -

> > - Show quoted text -

On Thu, Jan 8, 2009 at 3:27 PM, Rohit <mord...@gmail.com> wrote:

> I am setting the Background (using view.setBackgroundResource()) of
> about 5 views with pngs that fill up the entire screen (as a
> backdrop). I scroll between these 5 views and thus want to keep them
> in cache (I use view.setChildrenCacheEnabled()) but I run into the
> OutOfMemoryError: bitmap exceeds VM budget error. Is there a way to
> overcome it?

> Rohit

> n Dec 17 2008, 11:20 am, Mark K <mark.ka...@gmail.com> wrote:
>> Thanks for the beta on the bitmap,recycle(), it works! Before
>> processing the next bitmap I use this code to free up memory. I have a
>> class level Bitmap object.

>>                                 Bitmap bm;// class level

>>                                 if (bm!=null)
>>                 {
>>                          bm.recycle();
>>                          try
>>                          {
>>                                 Thread.sleep(100);
>>                          }
>>                          catch(Exception e){}
>>                          bm=null;
>>                          System.gc();
>>                          try
>>                          {
>>                                 Thread.sleep(100);
>>                          }
>>                          catch(Exception e){}
>>                 }
>>                                // create new bitmap and start again.

>> Thanks again, it works!

>> On Dec 17, 5:56 am, Mike Reed <r...@google.com> wrote:

>> > Its a little raw, but if you know you're absolutely done using a given
>> > bitmap object, you can call bitmap.recycle(). This immediately frees
>> > up the memory associated with the bitmap, and marks it as "dead",
>> > meaning it cannot be referenced again (i.e. don't try to draw or get/
>> > set its pixels anymore).

>> > i.e.

>> > for (all of my big images) {
>> >      Bitmap b = decode(...);
>> >      canvas.drawBitmap(b, ...);
>> >      b.recycle();
>> >      // yikes, don't reference b again)

>> > }

>> > On Dec 15, 2008, at 9:04 PM, Mark K wrote:

>> >   Is there a work around for this problem? Something I need to do
>> > differently perhaps? It seems like garbage collection is not occurring
>> > between successive bitmap decoding operations. Explicitly calling gc()
>> > does not seem to help. This is particularly a problem on the G1,
>> > because there is no way to reduce the camera resolution, all of the
>> > camera pictures are large. If I loop through a directory of pictures
>> > taken by the camera and use BitmapFactory.decodeFile(), I will get an
>> > out of memory error on the 2nd or 3rd iteration. Since I am only
>> > displaying/decoding one bitmap at a time I would hope that garbage
>> > collection would free up the memory between operations such that this
>> > does not occur. Any help would be greatly appreciated. Here's the code
>> > I use: This code runs a slide show of the images in the camera
>> > directory, it uses Handler.postDelayed() to render each picture. Is
>> > there anyway to tweak the code to get rid of the out of memory
>> > problem.

>> > public boolean slideShow()
>> >     {
>> >         String baseDir = "/sdcard/dcim/Camera/";
>> >         long showTime = 1500;

>> >         File dir = new File(baseDir);
>> >         File[] pics = dir.listFiles();
>> >         for ( int i=0; i<pics.length; i++ )
>> >         {
>> >                 String pic=baseDir+pics[i].getName();
>> >                 handler.postDelayed(new ShowSlide(pic), i*showTime);
>> >         }
>> >         return true;
>> >     }

>> > class ShowSlide extends Thread
>> >     {
>> >         String pc="";
>> >         public ShowSlide(String pc)
>> >         {
>> >                 this.pc=pc;
>> >         }
>> >         public void run()
>> >         {
>> >                 System.out.println("Showing picture: "+pc.toString());
>> >                 displayPicture(pc);
>> >         }
>> >     }

>> > public boolean displayPicture(String filepath)
>> >     {
>> >                File file = new File(filepath);
>> >                 BitmapFactory bfac = new BitmapFactory();
>> >         try
>> >         {
>> >                 bm = bfac.decodeFile(filepath);// out of memory error occurs
>> > here!
>> >                 handler.post(new SetImage(iView, bm));
>> >         }
>> >         catch(Exception e)
>> >         {
>> >            Log.e(TAG,"display picture failed: "+filepath+" "+e.toString
>> > ());
>> >            e.printStackTrace();
>> >            return false;
>> >         }

>> >         return true;
>> >     }

>> > class SetImage extends Thread
>> >     {
>> >         ImageView vv;
>> >         Bitmap bb;
>> >         public SetImage(ImageView vv, Bitmap bb)
>> >         {
>> >                 this.vv=vv;
>> >                 this.bb=bb;
>> >         }
>> >         public void run()
>> >         {
>> >                 vv.setImageBitmap(bb);
>> >         }
>> >     }

>> > On Dec 15, 2:48 pm, Romain Guy <romain...@google.com> wrote:

>> > >>  I've run into this exact same problem a number of times myself. Not
>> > >> sure if its a bug or just a limitation of the jvm, can't seem to
>> > >> process more than a few large bitmaps without this occuring, this
>> > >> always seems to occur when decoding bitmaps from file.

>> > > Neither, you are just using too much memory.

>> > > --
>> > > Romain Guy
>> > > Android framework engineer
>> > > romain...@android.com

>> > > Note: please don't send private questions to me, as I don't have time
>> > > to provide private support.  All such questions should be posted on
>> > > public forums, where I and others can see and answer them- Hide quoted text -

>> > - Show quoted text -

> Use less memory. One full screen PNG uses roughly 480*320*4 bytes (~=
> 614k.) Since you enable caching, you are doubling that amount to
> ~1.2MB per view. With 5 views you are using about 6 MB of memory (out
> of 16 MB maximum) just for the background images.

> On Thu, Jan 8, 2009 at 3:27 PM, Rohit <mord...@gmail.com> wrote:

> > I am setting the Background (using view.setBackgroundResource()) of
> > about 5 views with pngs that fill up the entire screen (as a
> > backdrop). I scroll between these 5 views and thus want to keep them
> > in cache (I use view.setChildrenCacheEnabled()) but I run into the
> > OutOfMemoryError: bitmap exceeds VM budget error. Is there a way to
> > overcome it?

> > Rohit

> > n Dec 17 2008, 11:20 am, Mark K <mark.ka...@gmail.com> wrote:
> >> Thanks for the beta on the bitmap,recycle(), it works! Before
> >> processing the next bitmap I use this code to free up memory. I have a
> >> class level Bitmap object.

> >>                                 Bitmap bm;// class level

> >>                                 if (bm!=null)
> >>                 {
> >>                          bm.recycle();
> >>                          try
> >>                          {
> >>                                 Thread.sleep(100);
> >>                          }
> >>                          catch(Exception e){}
> >>                          bm=null;
> >>                          System.gc();
> >>                          try
> >>                          {
> >>                                 Thread.sleep(100);
> >>                          }
> >>                          catch(Exception e){}
> >>                 }
> >>                                // create new bitmap and start again.

> >> Thanks again, it works!

> >> On Dec 17, 5:56 am, Mike Reed <r...@google.com> wrote:

> >> > Its a little raw, but if you know you're absolutely done using a given
> >> > bitmap object, you can call bitmap.recycle(). This immediately frees
> >> > up the memory associated with the bitmap, and marks it as "dead",
> >> > meaning it cannot be referenced again (i.e. don't try to draw or get/
> >> > set its pixels anymore).

> >> > i.e.

> >> > for (all of my big images) {
> >> >      Bitmap b = decode(...);
> >> >      canvas.drawBitmap(b, ...);
> >> >      b.recycle();
> >> >      // yikes, don't reference b again)

> >> > }

> >> > On Dec 15, 2008, at 9:04 PM, Mark K wrote:

> >> >   Is there a work around for this problem? Something I need to do
> >> > differently perhaps? It seems like garbage collection is not occurring
> >> > between successive bitmap decoding operations. Explicitly calling gc()
> >> > does not seem to help. This is particularly a problem on the G1,
> >> > because there is no way to reduce the camera resolution, all of the
> >> > camera pictures are large. If I loop through a directory of pictures
> >> > taken by the camera and use BitmapFactory.decodeFile(), I will get an
> >> > out of memory error on the 2nd or 3rd iteration. Since I am only
> >> > displaying/decoding one bitmap at a time I would hope that garbage
> >> > collection would free up the memory between operations such that this
> >> > does not occur. Any help would be greatly appreciated. Here's the code
> >> > I use: This code runs a slide show of the images in the camera
> >> > directory, it uses Handler.postDelayed() to render each picture. Is
> >> > there anyway to tweak the code to get rid of the out of memory
> >> > problem.

> >> > public boolean slideShow()
> >> >     {
> >> >         String baseDir = "/sdcard/dcim/Camera/";
> >> >         long showTime = 1500;

> >> >         File dir = new File(baseDir);
> >> >         File[] pics = dir.listFiles();
> >> >         for ( int i=0; i<pics.length; i++ )
> >> >         {
> >> >                 String pic=baseDir+pics[i].getName();
> >> >                 handler.postDelayed(new ShowSlide(pic), i*showTime);
> >> >         }
> >> >         return true;
> >> >     }

> >> > class ShowSlide extends Thread
> >> >     {
> >> >         String pc="";
> >> >         public ShowSlide(String pc)
> >> >         {
> >> >                 this.pc=pc;
> >> >         }
> >> >         public void run()
> >> >         {
> >> >                 System.out.println("Showing picture: "+pc.toString());
> >> >                 displayPicture(pc);
> >> >         }
> >> >     }

> >> > public boolean displayPicture(String filepath)
> >> >     {
> >> >                File file = new File(filepath);
> >> >                 BitmapFactory bfac = new BitmapFactory();
> >> >         try
> >> >         {
> >> >                 bm = bfac.decodeFile(filepath);// out of memory error occurs
> >> > here!
> >> >                 handler.post(new SetImage(iView, bm));
> >> >         }
> >> >         catch(Exception e)
> >> >         {
> >> >            Log.e(TAG,"display picture failed: "+filepath+" "+e.toString
> >> > ());
> >> >            e.printStackTrace();
> >> >            return false;
> >> >         }

> >> >         return true;
> >> >     }

> >> > class SetImage extends Thread
> >> >     {
> >> >         ImageView vv;
> >> >         Bitmap bb;
> >> >         public SetImage(ImageView vv, Bitmap bb)
> >> >         {
> >> >                 this.vv=vv;
> >> >                 this.bb=bb;
> >> >         }
> >> >         public void run()
> >> >         {
> >> >                 vv.setImageBitmap(bb);
> >> >         }
> >> >     }

> >> > On Dec 15, 2:48 pm, Romain Guy <romain...@google.com> wrote:

> >> > >>  I've run into this exact same problem a number of times myself. Not
> >> > >> sure if its a bug or just a limitation of the jvm, can't seem to
> >> > >> process more than a few large bitmaps without this occuring, this
> >> > >> always seems to occur when decoding bitmaps from file.

> >> > > Neither, you are just using too much memory.

> >> > > --
> >> > > Romain Guy
> >> > > Android framework engineer
> >> > > romain...@android.com

> >> > > Note: please don't send private questions to me, as I don't have time
> >> > > to provide private support.  All such questions should be posted on
> >> > > public forums, where I and others can see and answer them- Hide quoted text -

> >> > - Show quoted text -

> --
> Romain Guy
> Android framework engineer
> romain...@android.com

> Note: please don't send private questions to me, as I don't have time
> to provide private support.  All such questions should be posted on
> public forums, where I and others can see and answer them- Hide quoted text -

> - Show quoted text -

>   I'm still seeing this problem. I've used the bitmap.recycle() which
> seems to mitigate this problem, but not get rid if it entirely. I'm
> only processing one bitmap at a time, I recycle the bitmap, null it,
> and call gc().  Runtime.freeMemory() indicates that I have over 10 MB
> free memory, none of my bitmaps are over 3.5 MB, I only process one at
> a time, yet this problem still occurs intermittently. Is this a bug or
> low level memory leak? I've spent a considerable amount of time on
> this issue, but cannot seem to resolve it. I'd at least like to know
> if this is a documented bug, or if there is any hope of a resolution
> in future Android version. The problem seems to arise from
> BitmapFactory.decodeFile() . I've communicated with other developers
> that seem to have almost the exact same problem. I'd like to at least
> know if this is on the radar as a bug, and if there is any chance it
> will be dealt with in a future version of Android. Thanks

>                                                          Mark

> On Jan 8, 3:29 pm, Romain Guy <romain...@google.com> wrote:

> > Use less memory. One full screen PNG uses roughly 480*320*4 bytes (~=
> > 614k.) Since you enable caching, you are doubling that amount to
> > ~1.2MB per view. With 5 views you are using about 6 MB of memory (out
> > of 16 MB maximum) just for the background images.

> > On Thu, Jan 8, 2009 at 3:27 PM, Rohit <mord...@gmail.com> wrote:

> > > I am setting the Background (using view.setBackgroundResource()) of
> > > about 5 views with pngs that fill up the entire screen (as a
> > > backdrop). I scroll between these 5 views and thus want to keep them
> > > in cache (I use view.setChildrenCacheEnabled()) but I run into the
> > >OutOfMemoryError: bitmap exceeds VM budget error. Is there a way to
> > > overcome it?

> > > Rohit

> > > n Dec 17 2008, 11:20 am, Mark K <mark.ka...@gmail.com> wrote:
> > >> Thanks for the beta on the bitmap,recycle(), it works! Before
> > >> processing the next bitmap I use this code to free up memory. I have a
> > >> class level Bitmap object.

> > >>                                 Bitmap bm;// class level

> > >>                                 if (bm!=null)
> > >>                 {
> > >>                          bm.recycle();
> > >>                          try
> > >>                          {
> > >>                                 Thread.sleep(100);
> > >>                          }
> > >>                          catch(Exception e){}
> > >>                          bm=null;
> > >>                          System.gc();
> > >>                          try
> > >>                          {
> > >>                                 Thread.sleep(100);
> > >>                          }
> > >>                          catch(Exception e){}
> > >>                 }
> > >>                                // create new bitmap and start again.

> > >> Thanks again, it works!

> > >> On Dec 17, 5:56 am, Mike Reed <r...@google.com> wrote:

> > >> > Its a little raw, but if you know you're absolutely done using a given
> > >> > bitmap object, you can call bitmap.recycle(). This immediately frees
> > >> > up the memory associated with the bitmap, and marks it as "dead",
> > >> > meaning it cannot be referenced again (i.e. don't try to draw or get/
> > >> > set its pixels anymore).

> > >> > i.e.

> > >> > for (all of my big images) {
> > >> >      Bitmap b = decode(...);
> > >> >      canvas.drawBitmap(b, ...);
> > >> >      b.recycle();
> > >> >      // yikes, don't reference b again)

> > >> > }

> > >> > On Dec 15, 2008, at 9:04 PM, Mark K wrote:

> > >> >   Is there a work around for this problem? Something I need to do
> > >> > differently perhaps? It seems like garbage collection is not occurring
> > >> > between successive bitmap decoding operations. Explicitly calling gc()
> > >> > does not seem to help. This is particularly a problem on the G1,
> > >> > because there is no way to reduce the camera resolution, all of the
> > >> > camera pictures are large. If I loop through a directory of pictures
> > >> > taken by the camera and use BitmapFactory.decodeFile(), I will get an
> > >> > out of memory error on the 2nd or 3rd iteration. Since I am only
> > >> > displaying/decoding one bitmap at a time I would hope that garbage
> > >> > collection would free up the memory between operations such that this
> > >> > does not occur. Any help would be greatly appreciated. Here's the code
> > >> > I use: This code runs a slide show of the images in the camera
> > >> > directory, it uses Handler.postDelayed() to render each picture. Is
> > >> > there anyway to tweak the code to get rid of the out of memory
> > >> > problem.

> > >> > public boolean slideShow()
> > >> >     {
> > >> >         String baseDir = "/sdcard/dcim/Camera/";
> > >> >         long showTime = 1500;

> > >> >         File dir = new File(baseDir);
> > >> >         File[] pics = dir.listFiles();
> > >> >         for ( int i=0; i<pics.length; i++ )
> > >> >         {
> > >> >                 String pic=baseDir+pics[i].getName();
> > >> >                 handler.postDelayed(new ShowSlide(pic), i*showTime);
> > >> >         }
> > >> >         return true;
> > >> >     }

> > >> > class ShowSlide extends Thread
> > >> >     {
> > >> >         String pc="";
> > >> >         public ShowSlide(String pc)
> > >> >         {
> > >> >                 this.pc=pc;
> > >> >         }
> > >> >         public void run()
> > >> >         {
> > >> >                 System.out.println("Showing picture: "+pc.toString());
> > >> >                 displayPicture(pc);
> > >> >         }
> > >> >     }

> > >> > public boolean displayPicture(String filepath)
> > >> >     {
> > >> >                File file = new File(filepath);
> > >> >                 BitmapFactory bfac = new BitmapFactory();
> > >> >         try
> > >> >         {
> > >> >                 bm = bfac.decodeFile(filepath);// out of memory error occurs
> > >> > here!
> > >> >                 handler.post(new SetImage(iView, bm));
> > >> >         }
> > >> >         catch(Exception e)
> > >> >         {
> > >> >            Log.e(TAG,"display picture failed: "+filepath+" "+e.toString
> > >> > ());
> > >> >            e.printStackTrace();
> > >> >            return false;
> > >> >         }

> > >> >         return true;
> > >> >     }

> > >> > class SetImage extends Thread
> > >> >     {
> > >> >         ImageView vv;
> > >> >         Bitmap bb;
> > >> >         public SetImage(ImageView vv, Bitmap bb)
> > >> >         {
> > >> >                 this.vv=vv;
> > >> >                 this.bb=bb;
> > >> >         }
> > >> >         public void run()
> > >> >         {
> > >> >                 vv.setImageBitmap(bb);
> > >> >         }
> > >> >     }

> > >> > On Dec 15, 2:48 pm, Romain Guy

> I'm still seeing this problem as well. I can boot my phone, start my
> app, load a single image (~300k) and have this error. I'm loading
> images with the BitmapFactory.decodeByteArray() method, which calls
> BitmapFactory.nativeDecodeByteArray().

> What is interesting is that after I added a background thread to my
> app to load and process images, I had a bug where changing the
> orientation of the screen caused another thread to be started. As soon
> as two of my threads were in BitmapFactory.nativeDecodeByteArray() at
> the same time, this method would attempt to allocate over 6MB of
> memory, and I would get the error.

> E/dalvikvm-heap( 1204): 6291456-byte external allocation too large for
> this process.
> E/        ( 1204): VM won't let us allocate 6291456 bytes
> D/skia    ( 1204): xxxxxxxxxxxxxxxxxxxx allocPixelRef failed
> W/dalvikvm( 1204): threadid=15: thread exiting with uncaught exception
> (group=0x40013e28)
> E/AndroidRuntime( 1204): Uncaught handler: thread Thread-12 exiting
> due to uncaught exception
> E/AndroidRuntime( 1204): java.lang.OutOfMemoryError: bitmap size
> exceeds VM budget
> E/AndroidRuntime( 1204):        at
> android.graphics.BitmapFactory.nativeDecodeByteArray(Native Method)
> E/AndroidRuntime( 1204):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:234)
> E/AndroidRuntime( 1204):        at
> android.graphics.BitmapFactory.decodeByteArray(BitmapFactory.java:247)
> E/AndroidRuntime( 1204):        at
> org.hopto.group18.postbot.Image.loadFileContents(Image.java:85)
> E/AndroidRuntime( 1204):        at org.hopto.group18.postbot.EditPost$20.run
> (EditPost.java:800)
> E/AndroidRuntime( 1204):        at java.lang.Thread.run(Thread.java:935)

> I'm using 500k buffers (down from 1MB, down from 1.5MB in an effort to
> avoid OOMEs) to load images, the images themselves are ~300k (taken
> with the phone's camera). I can't imagine why it is trying to allocate
> 6MB.

> I have fixed my thread issue (even when not changing orientation this
> issue occurs), and I am using locking to prevent two of my threads
> from using this method at the same time, but I still see this error,
> although less frequently.

> It seems to come and go: sometimes I can't seem to load a single image
> for a period of a minute or two, and then the problem will go away. Is
> it possible that these errors can be the result of concurrent access
> to this native method by my app and other apps?

> On Jan 8, 7:05 pm, Mark K <mark.ka...@gmail.com> wrote:

> >   I'm still seeing this problem. I've used the bitmap.recycle() which
> > seems to mitigate this problem, but not get rid if it entirely. I'm
> > only processing one bitmap at a time, I recycle the bitmap, null it,
> > and call gc().  Runtime.freeMemory() indicates that I have over 10 MB
> > free memory, none of my bitmaps are over 3.5 MB, I only process one at
> > a time, yet this problem still occurs intermittently. Is this a bug or
> > low level memory leak? I've spent a considerable amount of time on
> > this issue, but cannot seem to resolve it. I'd at least like to know
> > if this is a documented bug, or if there is any hope of a resolution
> > in future Android version. The problem seems to arise from
> > BitmapFactory.decodeFile() . I've communicated with other developers
> > that seem to have almost the exact same problem. I'd like to at least
> > know if this is on the radar as a bug, and if there is any chance it
> > will be dealt with in a future version of Android. Thanks

> >                                                          Mark

> > On Jan 8, 3:29 pm, Romain Guy <romain...@google.com> wrote:

> > > Use less memory. One full screen PNG uses roughly 480*320*4 bytes (~=
> > > 614k.) Since you enable caching, you are doubling that amount to
> > > ~1.2MB per view. With 5 views you are using about 6 MB of memory (out
> > > of 16 MB maximum) just for the background images.

> > > On Thu, Jan 8, 2009 at 3:27 PM, Rohit <mord...@gmail.com> wrote:

> > > > I am setting the Background (using view.setBackgroundResource()) of
> > > > about 5 views with pngs that fill up the entire screen (as a
> > > > backdrop). I scroll between these 5 views and thus want to keep them
> > > > in cache (I use view.setChildrenCacheEnabled()) but I run into the
> > > >OutOfMemoryError: bitmap exceeds VM budget error. Is there a way to
> > > > overcome it?

> > > > Rohit

> > > > n Dec 17 2008, 11:20 am, Mark K <mark.ka...@gmail.com> wrote:
> > > >> Thanks for the beta on the bitmap,recycle(), it works! Before
> > > >> processing the next bitmap I use this code to free up memory. I have a
> > > >> class level Bitmap object.

> > > >>                                 Bitmap bm;// class level

> > > >>                                 if (bm!=null)
> > > >>                 {
> > > >>                          bm.recycle();
> > > >>                          try
> > > >>                          {
> > > >>                                 Thread.sleep(100);
> > > >>                          }
> > > >>                          catch(Exception e){}
> > > >>                          bm=null;
> > > >>                          System.gc();
> > > >>                          try
> > > >>                          {
> > > >>                                 Thread.sleep(100);
> > > >>                          }
> > > >>                          catch(Exception e){}
> > > >>                 }
> > > >>                                // create new bitmap and start again.

> > > >> Thanks again, it works!

> > > >> On Dec 17, 5:56 am, Mike Reed <r...@google.com> wrote:

> > > >> > Its a little raw, but if you know you're absolutely done using a given
> > > >> > bitmap object, you can call bitmap.recycle(). This immediately frees
> > > >> > up the memory associated with the bitmap, and marks it as "dead",
> > > >> > meaning it cannot be referenced again (i.e. don't try to draw or get/
> > > >> > set its pixels anymore).

> > > >> > i.e.

> > > >> > for (all of my big images) {
> > > >> >      Bitmap b = decode(...);
> > > >> >      canvas.drawBitmap(b, ...);
> > > >> >      b.recycle();
> > > >> >      // yikes, don't reference b again)

> > > >> > }

> > > >> > On Dec 15, 2008, at 9:04 PM, Mark K wrote:

> > > >> >   Is there a work around for this problem? Something I need to do
> > > >> > differently perhaps? It seems like garbage collection is not occurring
> > > >> > between successive bitmap decoding operations. Explicitly calling gc()
> > > >> > does not seem to help. This is particularly a problem on the G1,
> > > >> > because there is no way to reduce the camera

> I'm still seeing this problem as well. I can boot my phone, start my
> app, load a single image (~300k) and have this error. I'm loading
> images with the BitmapFactory.decodeByteArray() method, which calls
> BitmapFactory.nativeDecodeByteArray().

> What is interesting is that after I added a background thread to my
> app to load and process images, I had a bug where changing the
> orientation of the screen caused another thread to be started. As soon
> as two of my threads were in BitmapFactory.nativeDecodeByteArray() at
> the same time, this method would attempt to allocate over 6MB of
> memory, and I would get the error.

> E/dalvikvm-heap( 1204): 6291456-byte external allocation too large for
> this process.

> Sounds like your have ~300 KB JPEG-compressed images at the standard
> G1 resolution of 2048 * 1536. At 2 bytes per pixel (using RGB_565 or
> ARGB_4444 format) this will in your phone expand into 2048 * 1536 * 2
> = 6291456 bytes uncompressed. That's a sizable chunk of memory.

> Regards

> On Jan 11, 4:29 pm, nickthecook <nickthec...@gmail.com> wrote:

> > I'm still seeing this problem as well. I can boot my phone, start my
> > app, load a single image (~300k) and have this error. I'm loading
> > images with the BitmapFactory.decodeByteArray() method, which calls
> > BitmapFactory.nativeDecodeByteArray().

> > What is interesting is that after I added a background thread to my
> > app to load and process images, I had a bug where changing the
> > orientation of the screen caused another thread to be started. As soon
> > as two of my threads were in BitmapFactory.nativeDecodeByteArray() at
> > the same time, this method would attempt to allocate over 6MB of
> > memory, and I would get the error.

> > E/dalvikvm-heap( 1204): 6291456-byte external allocation too large for
> > this process.

> Interesting!

> I'm usually able to load these images without a problem. Maybe 1 in 5
> loads fails. Since they are all the same size, I would expect all
> calls to fail like this, or none, but that number is definitely not a
> coincidence.

> Anyway, I'm now using the version of decodeByteArray that takes
> options with inSampleSize = 2, and can't get it to crash no matter how
> many images I try to process in a row, so the problem is gone for now,
> at least.

> Thanks for the insight!

> On Jan 13, 8:21 am, blindfold <seeingwithso...@gmail.com> wrote:

> > Sounds like your have ~300 KB JPEG-compressed images at the standard
> > G1 resolution of 2048 * 1536. At 2 bytes per pixel (using RGB_565 or
> > ARGB_4444 format) this will in your phone expand into 2048 * 1536 * 2
> > = 6291456 bytes uncompressed. That's a sizable chunk of memory.

> > Regards

> > On Jan 11, 4:29 pm, nickthecook <nickthec...@gmail.com> wrote:

> > > I'm still seeing this problem as well. I can boot my phone, start my
> > > app, load a single image (~300k) and have this error. I'm loading
> > > images with the BitmapFactory.decodeByteArray() method, which calls
> > > BitmapFactory.nativeDecodeByteArray().

> > > What is interesting is that after I added a background thread to my
> > > app to load and process images, I had a bug where changing the
> > > orientation of the screen caused another thread to be started. As soon
> > > as two of my threads were in BitmapFactory.nativeDecodeByteArray() at
> > > the same time, this method would attempt to allocate over 6MB of
> > > memory, and I would get the error.

> > > E/dalvikvm-heap( 1204): 6291456-byte external allocation too large for
> > > this process.

> YES YES YES!!!
> I've found solution for that bug.
> It's tricky but it works.
> Place that on the begining of your code.

>                 try{
>                                 Bitmap tmpBitmap = Bitmap.createBitmap
> (3200, 4800,
> Config.ARGB_8888);
>                 }catch(Throwable e){
>                         e.printStackTrace();
>                         System.out.println("CATCHED !!!!");

>                 }

> I was fighting with that about 4 days.
> Hope anyone is happy now, that was hell.

> Regards,
> avram.

> How can this possibly help you? You are trying to allocate 61 MB
> (3200*4800*4 bytes), which lies well above the 16 MB heap limit. I
> tried once to allocate, say, 12 MB at program startup to keep Android
> from all the time bumping into the heap limit and possibly crashing as
> a result in case its memory management is not 100% reliable, but
> trying to allocate 61 MB should not offer any benefit?

> Regards

> On Jan 25, 2:23 pm, ad <avra...@gmail.com> wrote:

> > YES YES YES!!!
> > I've found solution for that bug.
> > It's tricky but it works.
> > Place that on the begining of your code.

> >                 try{
> >                                BitmaptmpBitmap =Bitmap.createBitmap
> > (3200, 4800,
> > Config.ARGB_8888);
> >                 }catch(Throwable e){
> >                         e.printStackTrace();
> >                         System.out.println("CATCHED !!!!");

> >                 }

> > I was fighting with that about 4 days.
> > Hope anyone is happy now, that was hell.

> > Regards,
> > avram.

> Check first, and think a bit.

> Check first, and think a bit.

> On Jan 25, 2:49 pm, blindfold <seeingwithso...@gmail.com> wrote:

> > How can this possibly help you? You are trying to allocate 61 MB
> > (3200*4800*4 bytes), which lies well above the 16 MB heap limit. I
> > tried once to allocate, say, 12 MB at program startup to keep Android
> > from all the time bumping into the heap limit and possibly crashing as
> > a result in case its memory management is not 100% reliable, but
> > trying to allocate 61 MB should not offer any benefit?

> > Regards

> > On Jan 25, 2:23 pm, ad <avra...@gmail.com> wrote:

> > > YES YES YES!!!
> > > I've found solution for that bug.
> > > It's tricky but it works.
> > > Place that on the begining of your code.

> > >                 try{
> > >                                BitmaptmpBitmap =Bitmap.createBitmap
> > > (3200, 4800,
> > > Config.ARGB_8888);
> > >                 }catch(Throwable e){
> > >                         e.printStackTrace();
> > >                         System.out.println("CATCHED !!!!");

> > >                 }

> > > I was fighting with that about 4 days.
> > > Hope anyone is happy now, that was hell.

> > > Regards,
> > > avram.

> > Check first, and think a bit.

> I stand by what I said.

> Regards

> On Jan 25, 8:30 pm, ad <avra...@gmail.com> wrote:

> > Check first, and think a bit.

> > On Jan 25, 2:49 pm, blindfold <seeingwithso...@gmail.com> wrote:

> > > How can this possibly help you? You are trying to allocate 61 MB
> > > (3200*4800*4 bytes), which lies well above the 16 MB heap limit. I
> > > tried once to allocate, say, 12 MB at program startup to keep Android
> > > from all the time bumping into the heap limit and possibly crashing as
> > > a result in case its memory management is not 100% reliable, but
> > > trying to allocate 61 MB should not offer any benefit?

> > > Regards

> > > On Jan 25, 2:23 pm, ad <avra...@gmail.com> wrote:

> > > > YES YES YES!!!
> > > > I've found solution for that bug.
> > > > It's tricky but it works.
> > > > Place that on the begining of your code.

> > > >                 try{
> > > >                                BitmaptmpBitmap =Bitmap.createBitmap
> > > > (3200, 4800,
> > > > Config.ARGB_8888);
> > > >                 }catch(Throwable e){
> > > >                         e.printStackTrace();
> > > >                         System.out.println("CATCHED !!!!");

> > > >                 }

> > > > I was fighting with that about 4 days.
> > > > Hope anyone is happy now, that was hell.

> > > > Regards,
> > > > avram.

On Wed, Feb 4, 2009 at 11:05 AM, Rohit <mord...@gmail.com> wrote:

> I noticed that the OutOfMemoryError occurs a lot when you try to load
> an image that is larger than the view. Android needs to scale the
> image down to fit the view and that is when it seems to crash out as a
> result of the OutOfMemoryError.

> Rohit

> On Jan 26, 3:09 pm, blindfold <seeingwithso...@gmail.com> wrote:
>> > Check first, and think a bit.

>> I stand by what I said.

>> Regards

>> On Jan 25, 8:30 pm, ad <avra...@gmail.com> wrote:

>> > Check first, and think a bit.

>> > On Jan 25, 2:49 pm, blindfold <seeingwithso...@gmail.com> wrote:

>> > > How can this possibly help you? You are trying to allocate 61 MB
>> > > (3200*4800*4 bytes), which lies well above the 16 MB heap limit. I
>> > > tried once to allocate, say, 12 MB at program startup to keep Android
>> > > from all the time bumping into the heap limit and possibly crashing as
>> > > a result in case its memory management is not 100% reliable, but
>> > > trying to allocate 61 MB should not offer any benefit?

>> > > Regards

>> > > On Jan 25, 2:23 pm, ad <avra...@gmail.com> wrote:

>> > > > YES YES YES!!!
>> > > > I've found solution for that bug.
>> > > > It's tricky but it works.
>> > > > Place that on the begining of your code.

>> > > >                 try{
>> > > >                                BitmaptmpBitmap =Bitmap.createBitmap
>> > > > (3200, 4800,
>> > > > Config.ARGB_8888);
>> > > >                 }catch(Throwable e){
>> > > >                         e.printStackTrace();
>> > > >                         System.out.println("CATCHED !!!!");

>> > > >                 }

>> > > > I was fighting with that about 4 days.
>> > > > Hope anyone is happy now, that was hell.

>> > > > Regards,
>> > > > avram.

> Scaling the image down happens at drawing time. You are just using
> images that are too large to begin with.

> On Wed, Feb 4, 2009 at 11:05 AM, Rohit <mord...@gmail.com> wrote:

> > I noticed that the OutOfMemoryError occurs a lot when you try to load
> > an image that is larger than the view. Android needs to scale the
> > image down to fit the view and that is when it seems to crash out as a
> > result of the OutOfMemoryError.

> > Rohit

> > On Jan 26, 3:09 pm, blindfold <seeingwithso...@gmail.com> wrote:
> >> > Check first, and think a bit.

> >> I stand by what I said.

> >> Regards

> >> On Jan 25, 8:30 pm, ad <avra...@gmail.com> wrote:

> >> > Check first, and think a bit.

> >> > On Jan 25, 2:49 pm, blindfold <seeingwithso...@gmail.com> wrote:

> >> > > How can this possibly help you? You are trying to allocate 61 MB
> >> > > (3200*4800*4 bytes), which lies well above the 16 MB heap limit. I
> >> > > tried once to allocate, say, 12 MB at program startup to keep Android
> >> > > from all the time bumping into the heap limit and possibly crashing as
> >> > > a result in case its memory management is not 100% reliable, but
> >> > > trying to allocate 61 MB should not offer any benefit?

> >> > > Regards

> >> > > On Jan 25, 2:23 pm, ad <avra...@gmail.com> wrote:

> >> > > > YES YES YES!!!
> >> > > > I've found solution for that bug.
> >> > > > It's tricky but it works.
> >> > > > Place that on the begining of your code.

> >> > > >                 try{
> >> > > >                                BitmaptmpBitmap =Bitmap.createBitmap
> >> > > > (3200, 4800,
> >> > > > Config.ARGB_8888);
> >> > > >                 }catch(Throwable e){
> >> > > >                         e.printStackTrace();
> >> > > >                         System.out.println("CATCHED !!!!");

> >> > > >                 }

> >> > > > I was fighting with that about 4 days.
> >> > > > Hope anyone is happy now, that was hell.

> >> > > > Regards,
> >> > > > avram.

> --
> Romain Guy
> Android framework engineer
> romain...@android.com

> Note: please don't send private questions to me, as I don't have time
> to provide private support.  All such questions should be posted on
> public forums, where I and others can see and answer them

On Wed, Feb 4, 2009 at 11:11 AM, Rohit <mord...@gmail.com> wrote:

> So whats a good solution?

> Rohit

> On Feb 4, 11:07 am, Romain Guy <romain...@google.com> wrote:
>> Scaling the image down happens at drawing time. You are just using
>> images that are too large to begin with.

>> On Wed, Feb 4, 2009 at 11:05 AM, Rohit <mord...@gmail.com> wrote:

>> > I noticed that the OutOfMemoryError occurs a lot when you try to load
>> > an image that is larger than the view. Android needs to scale the
>> > image down to fit the view and that is when it seems to crash out as a
>> > result of the OutOfMemoryError.

>> > Rohit

>> > On Jan 26, 3:09 pm, blindfold <seeingwithso...@gmail.com> wrote:
>> >> > Check first, and think a bit.

>> >> I stand by what I said.

>> >> Regards

>> >> On Jan 25, 8:30 pm, ad <avra...@gmail.com> wrote:

>> >> > Check first, and think a bit.

>> >> > On Jan 25, 2:49 pm, blindfold <seeingwithso...@gmail.com> wrote:

>> >> > > How can this possibly help you? You are trying to allocate 61 MB
>> >> > > (3200*4800*4 bytes), which lies well above the 16 MB heap limit. I
>> >> > > tried once to allocate, say, 12 MB at program startup to keep Android
>> >> > > from all the time bumping into the heap limit and possibly crashing as
>> >> > > a result in case its memory management is not 100% reliable, but
>> >> > > trying to allocate 61 MB should not offer any benefit?

>> >> > > Regards

>> >> > > On Jan 25, 2:23 pm, ad <avra...@gmail.com> wrote:

>> >> > > > YES YES YES!!!
>> >> > > > I've found solution for that bug.
>> >> > > > It's tricky but it works.
>> >> > > > Place that on the begining of your code.

>> >> > > >                 try{
>> >> > > >                                BitmaptmpBitmap =Bitmap.createBitmap
>> >> > > > (3200, 4800,
>> >> > > > Config.ARGB_8888);
>> >> > > >                 }catch(Throwable e){
>> >> > > >                         e.printStackTrace();
>> >> > > >                         System.out.println("CATCHED !!!!");

>> >> > > >                 }

>> >> > > > I was fighting with that about 4 days.
>> >> > > > Hope anyone is happy now, that was hell.

>> >> > > > Regards,
>> >> > > > avram.

>> --
>> Romain Guy
>> Android framework engineer
>> romain...@android.com

>> Note: please don't send private questions to me, as I don't have time
>> to provide private support.  All such questions should be posted on
>> public forums, where I and others can see and answer them