Limbo crashes on Nexus 4

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run a VM under SDL or VNC Activity
2. Tap on the menu continuously
3. Limbo Crashes

What is the expected output? What do you see instead?
Limbo shouldn't crash, see log:
05-01 22:17:27.145: E/SurfaceTextureClient(17164): dequeueBuffer_DEPRECATED: 
Fence::wait returned an error: -4
05-01 22:17:27.145: W/Adreno200-EGLSUB(17164): <DequeueBuffer:461>: dequeue 
native buffer fail: Interrupted system call
05-01 22:17:27.145: W/Adreno200-ES20(17164): <gl2_surface_swap:43>: 
GL_OUT_OF_MEMORY
05-01 22:17:27.145: W/Adreno200-EGL(17164): <eglSwapBuffers:3498>: EGL_BAD_ALLOC
05-01 22:17:27.155: W/HardwareRenderer(17164): EGL error: EGL_BAD_ALLOC
05-01 22:17:27.165: W/HardwareRenderer(17164): Mountain View, we've had a 
problem here. Switching back to software rendering.
05-01 22:17:27.315: D/OpenGLRenderer(17164): GL error from OpenGLRenderer: 0x505
05-01 22:17:27.315: E/OpenGLRenderer(17164):   Out of memory!

Please use labels and text to provide additional information.

Original issue reported on code.google.com by ideal2i...@gmail.com on 2 May 2013 at 6:26

[GoogleCodeExporter]

for SDL this is the log:
05-01 22:17:27.145: E/SurfaceTextureClient(17164): dequeueBuffer_DEPRECATED: 
Fence::wait returned an error: -4
05-01 22:17:27.145: W/Adreno200-EGLSUB(17164): <DequeueBuffer:461>: dequeue 
native buffer fail: Interrupted system call
05-01 22:17:27.145: W/Adreno200-ES20(17164): <gl2_surface_swap:43>: 
GL_OUT_OF_MEMORY
05-01 22:17:27.145: W/Adreno200-EGL(17164): <eglSwapBuffers:3498>: EGL_BAD_ALLOC
05-01 22:17:27.155: W/HardwareRenderer(17164): EGL error: EGL_BAD_ALLOC
05-01 22:17:27.165: W/HardwareRenderer(17164): Mountain View, we've had a 
problem here. Switching back to software rendering.
05-01 22:17:27.315: D/OpenGLRenderer(17164): GL error from OpenGLRenderer: 0x505
05-01 22:17:27.315: E/OpenGLRenderer(17164):   Out of memory!

For VNC the logcat just shows a win death entry:
WIN DEATH: null

Original comment by ideal2i...@gmail.com on 2 May 2013 at 6:27

[GoogleCodeExporter]

This might be an issue with Android 4.2.2 or the Nexus 4 firmware.

Original comment by ideal2i...@gmail.com on 2 May 2013 at 6:28