[android-developers] OutOfMemoryError from BitmapFactory

2009-05-01 Thread Ward Willats
At 2:35 PM -0700 4/30/09, fadden wrote: The hprof dump can help with that. I added a quick writeup: http://android.git.kernel.org/?p=platform/dalvik.git;a=blob_plain;f=docs/heap-profiling.html;hb=HEAD Thanks -- I used hprof with a previous layout leakage problem, and I think it is a huge turd

[android-developers] OutOfMemoryError from BitmapFactory

2009-04-30 Thread Ward Willats
At 11:23 AM -0700 4/30/09, fadden wrote: It's possible that it didn't actually jump back down. The event log shows results from all running processes, not just your app, so you may be seeing output from other things mixed in. Ah, OK. Now I see a steady increase in my limit and allocs from 1.1

[android-developers] OutOfMemoryError from BitmapFactory

2009-04-30 Thread Ward Willats
Thanks for these tips. At 1:14 PM -0700 4/30/09, Streets Of Boston wrote: In my app, i've been dillegently 'unloading' bitmaps when i need memory. - clear any bitmap cache I assume you mean any of my own bitmap caches... So far, this scheme has served me well. Before i got a lot of OOM-

[android-developers] OutOfMemoryError from BitmapFactory

2009-04-29 Thread Ward Willats
I'm going to try to throw something together in python or C that does the number-crunching on the log. Well, I'm as old as Mark Murphy for cris'sake, so I like to use AWK for things like this, which seemed a good idea until I remembered it doesn't support infix bitwise operators. Doh! Guess

[android-developers] OutOfMemoryError from BitmapFactory

2009-04-29 Thread Ward Willats
At 10:26 PM -0700 4/28/09, fadden wrote: Well, that's the interesting question: how much memory are you *actually* spending on bitmaps? While I wait for a crash I can measure, my colleague here points out we use a lot of 9 patches as backgrounds for various fields on our screens. If they go

[android-developers] OutOfMemoryError from BitmapFactory

2009-04-28 Thread Ward Willats
At 12:05 PM -0700 4/28/09, Jon Webb wrote: I have a clue -- the OutOfMemoryError went away when I set debuggable to false. Does that help? No joy here, I'm afraid. I really hoped this would be it. (Debuggable changing garbage collection behavior or something...) I just happened to have a

[android-developers] OutOfMemoryError from BitmapFactory

2009-04-28 Thread Ward Willats
Thanks for this excellent explanation. Weird parallel universe indeed! So, right in the onCreate() of my application object, I went and allocated an 8MB array of bytes, causing the heap to grow to 10MB. I then null the array ref and call gc(), which freed up the allocation but left the heap