And they were not allocated in a "smaller area". They used to be allocated on the native heap but they counted against the Dalvik heap's usage (which is why you would get OOM anyway.) On Nov 21, 2012 10:23 AM, "b0b" <[email protected]> wrote:
> Bitmap data is not allocated in the Java heap but in a much smaller area > of native memory. > > So you can have several MB of Java Heap free and still have Bitmap OOM. > > Bitmaps are a total PITA to manage with Android. But it's doable. > Except that when you thnk you are done fixing all OOM, a new surprise > always awaits you. > > -- > 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 -- 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
