Nexus One的/ Android的＆QUOT; CPU可挂＆QUOT;错误 [英] Nexus One / Android "CPU may be pegged" bug

问题描述

我正在写一个图形密集型游戏的的Nexus One，使用NDK（修订版4）和OpenGL ES 2.0。我们真正推动了硬件在这里，在大多数情况下它工作得很好，但每过一段时间，我收到了严重的崩溃与此日志消息：

I'm writing a graphically intense game for the Nexus One, using the NDK (revision 4) and OpenGL ES 2.0. We're really pushing the hardware here, and for the most part it works well, except every once in a while I get a serious crash with this log message:

W / SharedBufferStack（398）：waitForCondition（LockCondition）超时   （同一性= 9，状态= 0）。 CPU可能会挂。尝试一次。

W/SharedBufferStack( 398): waitForCondition(LockCondition) timed out (identity=9, status=0). CPU may be pegged. trying again.

整个系统锁定，一遍又一遍重复这一消息，一两分钟后，将可以重新启动或者我们需要手动重新启动它。我们采用了Android 2.1操作系统，更新1。

The entire system locks up, repeats this message over and over, and will either restart after a couple minutes or we have to reboot it manually. We're using Android OS 2.1, update 1.

我知道其他几个人在那里看到了这个错误，有时会涉及到音频。在我的情况下，它造成的 SharedBufferStack ，所以我猜这是一个OpenGL的问题。有没有人遇到过这种，和更好的固定呢？还是没有人知道发生了什么与怎么回事了 SharedBufferStack 来帮我缩小范围？

I know a few other people out there have seen this bug, sometimes in relation to audio. In my case it's caused by the SharedBufferStack, so I'm guessing it's an OpenGL issue. Has anyone encountered this, and better yet fixed it? Or does anyone know what's going on with the SharedBufferStack to help me narrow things down?

推荐答案

我不相信可以发生在音频code这样的错误，SharedBufferStack只在表面图书馆使用。最大的可能是，这是在EGL swapBuffers或SurfaceFlinger实现中的错误，你应该将其提交到的 bug跟踪系统。

I don't believe such error can occur in audio code, SharedBufferStack is only used in Surface libraries. Most probably this is a bug in EGL swapBuffers or SurfaceFlinger implementation, and you should file it to the bug tracker.

这篇关于Nexus One的/ Android的＆QUOT; CPU可挂＆QUOT;错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！