I'm not sure what to post yet. I don't know what's causing it. My gut tells me that it has something to do with the surface or gles, but since it doesn't happen as a result of any method call that I make, I can't tell. It's something in Android causing it, probably as a result of something I did previously but can not track down. Once I know better what's causing it, I'll post the bug.
Is there any way to track down the function segfaulting using those memory addresses? On Jan 21, 1:45 am, "Mark Murphy" <[email protected]> wrote: > > So my game always runs perfectly the first time. When I run it, it > > loads and plays. You can switch activities and it resumes correctly. > > Great, right! Well, either after you exit out and the activity is > > destroyed or right when you start a new game, about 5 seconds into > > loading, this happens. I clean up very well after myself in the > > process so that it isn't consuming memory after the game is quit and > > so that the next load works correctly. I'm having a very difficult > > time tracking this down. > > > Like I said in the above paragraph, this only happens AFTER I quit the > > game or while loading a new game, after quitting a first one. It > > never happens the first time. > > While I have no suggestions on how to resolve the problem, definitely post > this tohttp://b.android.comif it does not appear to be there already. > Segfaults are always a bug in Android -- at minimum, it should throw a > Java exception rather than segfaulting. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > Android App Developer Books:http://commonsware.com/books.html
-- 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
