I mentioned this earlier but no one seemed to know anything about this. It just happened again to me in the middle of testing a new game, which is the first time I've seen it happen during one of my games. The game had been loaded for about a minute and I was playing and everything was fine and then the phone locked up and this was in the log:
I/ActivityThread(29551): Publishing provider com.android.deskclock: com.android.deskclock.AlarmProvider I/ActivityManager( 74): Process com.amazon.mp3 (pid 26508) has died. W/BackupManagerService( 74): dataChanged but no participant pkg='com.android.providers.settings' uid=10025 I/ActivityManager( 74): Process com.google.android.apps.uploader (pid 26714) has died. W/SharedBufferStack(29487): waitForCondition(LockCondition) timed out (identity=1310, status=0). CPU may be pegged. trying again. W/SharedBufferStack(29487): waitForCondition(LockCondition) timed out (identity=1310, status=0). CPU may be pegged. trying again. W/SharedBufferStack( 74): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again. W/SharedBufferStack(29487): waitForCondition(LockCondition) timed out (identity=1310, status=0). CPU may be pegged. trying again. W/SharedBufferStack( 74): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again. The waitForCondition messages kept logging every second until the phone (Nexus One) rebooted itself. This continued until the device rebooted. As you can imagine, process 29487 is my game. 74 is (I think) system service. Both got hung up and my game certainly didn't do anything to cause this. I just use a GLSurfaceView and a normal logic thread. Nothing special, no hacks. This is not the first time I've seen it - it can be reliably reproduced when flipping orientations on a live wallpaper service and doing the proper context/display destroy and new EGL init on orientation change. It happens almost instantly there. It's actually plaguing my live wallpaper because I haven't found a workaround for it yet. I've also seen this happen once before to RenderScript, so perhaps it is OpenGL-related? I feel like there is a bug down there in the depths of Android.... -- 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
