Google should do somethign about this "feature"... A lot of people get OutOfMemory exception even if they don't do anything wrong. Dalvik could and should be better. It is pretty slow compared to native code 10 or 15 times depending on what you are doing. Hope that JIT is comming soon on Android since this interpreter is slow and not that good...
And don't call bugs "features" and fix that OutOfMemory problem! On Apr 29, 6:53 pm, Ward Willats <[email protected]> wrote: > 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 into bitmap storage, and aren't regularly > compacted as we move from screen to screen, well, that could suck > down a lot of the external heap (and fragment it to boot). Perhaps > single large bitmaps we could preload would be better. > > Is that a nutty hypothesis? > > -- Ward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
