Unity player bug?

Questions & Answers
1

We are producing an OpenGL 2 app for Android and iOS. We are testing with a variety of devices by HTC, Samsung, Apple (natch), etc.

One one model of Android device, and only on that model (an HTC Desire A8181), the game causes the phone to freeze completely (no response to any buttons, not even power button) after 2-3 minutes of runtime. While so frozen, logcat spews the following three messages continuously, and no others:

W/SharedBufferStack(   96): waitForCondition(LockCondition) timed out (identity=14, status=0). CPU may be pegged. trying again.
W/SharedBufferStack(  549): waitForCondition(LockCondition) timed out (identity=12, status=0). CPU may be pegged. trying again.
W/SharedBufferStack(   96): waitForCondition(LockCondition) timed out (identity=2, status=0). CPU may be pegged. trying again.

If the power button is held down for several minutes (!) eventually a watchdog timer causes the phone to reboot.

Googling suggests that other developers have experienced this, however I am unable to determine the cause and no workarounds for Unity projects seem to be available.

Has anyone here seen this? Does anyone know what causes it? Does anyone have a solution?

Thanks

2

By any chance, are you doing any OpenGL drawing independent of Unity, e.g. with a Plugin? We’re seeing the same thing, and I suspect it might be related to one or more of the factors mentioned at Google Issue Tracker.