Thanks for the hint. The problem was caused by an other thread in the game that did not shut down properly.
On 22 Aug., 22:40, CraigsRace <craig...@gmail.com> wrote: > I thought SurfaceHolder.Callback.surfaceDestroyed would be called. > > On Aug 23, 6:19 am, Mike <internet...@hotmail.com> wrote: > > > Hello, > > > i am using android.opengl.GLSurfaceView in my game, which is working > > well expect under one condition: > > Starting the game a second time after leaving it by pushing the home > > button, causes the game to flicker, because the rendering thread from > > the previous instance is still running and firing OpenGL commands. > > Now the question is, how can i ensure that only one instance of > > GLSurfaceView/GLSurfaceView.Renderer gets created? > > > To solve/workaround the problem i've tried to set the following > > properties in the manifest file to to ensure the activity gets shut > > down if it gets inactive. > > android:configChanges="keyboardHidden|orientation" > > android:launchMode="singleTask" > > android:multiprocess="false" > > android:noHistory="true"> > > But without success, the activity/rendering thread still keeps > > running. > > Do you know of any certain way to exit the rendering thread/free > > GLSurfaceView? > > > Any advice is appreciated. Thanks, > > Mike --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
