[android-developers] Re: problems with bitmaps

2009-04-28 Thread Jon Webb
I didn't see an answer to your question. You should always recycle your bitmaps when you're done with them. bmp.recycle(); That said, bitmaps do take up a lot of memory, and of course it has to be contiguous, so you must be careful using them. E.g., use System.gc () judiciously, etc. -- Jon

[android-developers] Re: problems with bitmaps

2009-04-26 Thread Win Myo Htet
I also get the OOME ( 6291456-byte) with bitmap file of 350KB (if it is 35KB, it is fine) when I do the rotation on the third time. I use Bitmap.createScaledBitmap so that the pic fit into the screen and I also try do myPic.recycle() in onSaveInstanceState to release the memory but it is not

[android-developers] Re: problems with bitmaps

2009-04-09 Thread mark . kahrl
There's been a number of threads on this issue, the BitmapFactory tends to throw this out of memory errors when it really shouldn't, looks like a bug or memory leak. I'm not sure if it's cataloged as an official bug though. Using bitmap.recycle(), and reducing the sample size will mitigate ,

[android-developers] Re: problems with bitmaps

2009-04-09 Thread Romain Guy
BitmapFactory does not leak. It throws an OutOfMemoryException when there's no more memory available. That's all. On Thu, Apr 9, 2009 at 4:36 PM, mark.ka...@gmail.com wrote:  There's been a number of threads on this issue, the BitmapFactory tends to throw this out of memory errors when it

[android-developers] Re: problems with bitmaps

2009-04-09 Thread Mark Murphy
mark.ka...@gmail.com wrote: There's been a number of threads on this issue, the BitmapFactory tends to throw this out of memory errors when it really shouldn't, looks like a bug or memory leak. I'm not sure if it's cataloged as an official bug though. If you have a reproducible test case,