As far as i know it's actually a bug in android, as the allocation issue is in the JVM, not the kernel.
Do notice that i wasn't talking about fragmentation or reaching the heap size limit... If your heap size is 23.9MB with 100% of it free (thus, plenty of room), i.e 0MB utilization with 23.9MB of FREE heap, it will still failon the next allocation of anything above 100KB (you could allocate 99KB many times, but the first 100KB will fail) On Thursday, March 14, 2013 3:58:56 PM UTC+2, Kristopher Micinski wrote: > > On Thu, Mar 14, 2013 at 4:15 AM, Piren <gpi...@gmail.com <javascript:>> > wrote: > > Actually even 5K can crash his app... it all depends on what he did > before > > the allocation. > > Android has a nasty bug of claiming you dont have enough memory even if > your > > heap has more than enough free space if it grew close to its maximum > value > > previously (and dont't forget fragmentation as well, 10MB of free heap > > doesn't mean you can allocate 10MB). > > Notice that I said "heap size" and not individual allocation because > of this :-). This is nothing specific to Andorid: Linux does this > too. > -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
