Just for the information of readers here, the question was answered by Romain Guy on the other mailing list. The answer is that the app will use the same amount of memory both on pre-Honeycomb and on Honeycomb and above.
On máj. 20, 20:10, Tamás Kovács <[email protected]> wrote: > I'm developing a graphics-intensive application for Android 2.2 and > above. > > I know that starting with Honeycomb, bitmaps are stored on VM_HEAP > instead of their native bitmap heap. > > Does this influence the effective memory usage of my application? I > mean, e.g., if my app for pre-Honeycomb devices uses X MB of the VM > heap, and has Y MB bitmaps (stored on native heap), then I hope it > won't start using X+Y MB from the VM heap if it's installed on a > Honeycomb or newer device. > > This does not sound logical. Instead, I guess that bitmap size is > counted against the VM limits even prior to Honeycomb, otherwise why > would "bitmap size exceeds VM budget" errors appear? So they're stored > on their native heap but still counted against VM_HEAP size maximum). -- 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
