Is there any work-around? I'm ready to ship this port I'm working on, bar some polish, but of course the gc hitting during runtime causes unacceptable hits to playability.
This talk doesn't mention this bug, but he says that he hasn't had the gc run during gameplay in five months. http://code.google.com/events/io/sessions/WritingRealTimeGamesAndroid.html My guess is that it's because he's using vbo's for rendering, thus avoiding the bug. Maybe that'll be the path I have to take as well. On Jun 9, 11:05 pm, fadden <fad...@android.com> wrote: > On Jun 9, 2:05 am, Genc <gmt...@gmail.com> wrote: > > > A simple & basic question: Is that change 9029 shipped with Android > > SDK 1.5? Should I install SDK 1.5 to benefit changes? > > It is not part of 1.5. It will be included in a future release. > > The patch seems to have the unintentional side-effect of causing > memory to be held past the point when it should be freed. Some > additional work is being done to address this. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---