I'm sorry that I cannot afford to sell to the only 1% of the Android Market using ICS. I already have 6 apps that are not selling, but I digress...
After further work I've discovered that allocateDirect is consuming exactly 65636 bytes for every vertexBuffer that is created (again, on the tablet, but not on the phones). Can anybody that has some understanding of how Java memory works please give me a hint of what might be going on so I can find a workaround for it? On Wednesday, February 29, 2012 12:57:18 PM UTC-7, Mark Ayers wrote: > > I've noticed a LOT of memory management issues with Honeycomb on my ASUS > Transformer. I think there might be a defect in Honeycomb, because after my > ICS OTA got pushed, all of those issues are gone. > > On Monday, February 27, 2012 8:53:30 PM UTC-8, Yan wrote: >> >> The following eats away the heap on the Toshiba Thrive but not on the >> LG G2X: >> >> byteBuf = ByteBuffer.allocateDirect(vertices.length * 4); >> byteBuf.order(ByteOrder.nativeOrder()); >> vertexBuffer = byteBuf.asFloatBuffer(); >> vertexBuffer.put(vertices); >> vertexBuffer.position(0); >> >> I've tried byteBuf.clear, byteBuf.reset, making byteBuf static, >> System.gc, and combinations of these, but nothing works. I wonder why >> this is only a problem on the Toshiba but not the LG? >> > -- 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
