DequeueBuffer: BufferQueue has been abandoned

[David Seabolt]

Hi guys, this is extremely frustrating to get any information on and I'm hoping you might be able to shed some light onto the matter:

I'm currently running on a Nexus 7, and have been writing an app using NativeActivity. I've been implementing code to try and handle properly pausing and resuming the application, including releasing all my GL resources and reallocating them when needed. This has been working; for the most part. But lately I've been getting the following output in my logcat:

E/BufferQueue(  177): [com.ace.engine/android.app.NativeActivity] dequeueBuffer: BufferQueue has been abandoned!

W/Adreno200-EGLSUB( 1587): <DequeueBuffer:544>: dequeue native buffer fail: No such device

W/Adreno200-ES20( 1587): <gl2_surface_swap:43>: GL_OUT_OF_MEMORY

W/Adreno200-EGL( 1587): <qeglDrvAPI_eglSwapBuffers:3518>: EGL_BAD_ALLOC

W/Adreno200-EGL( 1587): <qeglDrvAPI_eglSwapBuffers:3525>: EGL_BAD_SURFACE

This then causes the unblankDisplay to take to long to finish (292ms), which then causes the window to be killed in the middle of my render, which then causes a crash because the context isn't valid. 
So I have a couple of questions:

1.) Is the above line of reasoning correct? I can get the crash to repro everytime using my code and it will always have this output, but I'm simply inferring what is happening.

2.) How did I cause the BufferQueue to be abandoned?

3.) Am I totally off base and this output has nothing to do with the window being killing in the middle of my render?

[venkat]

Hi David,

i am facing the same issue in my Lolipop version, do you able to solve the issue, or any help on why the "dequeueBuffer: BufferQueue has been abandoned"

E BufferQueueProducer: [com.example.launcher/com.example.launcher.Launcher] dequeueBuffer: BufferQueue has been abandoned

W Adreno-EGLSUB: <DequeueBuffer:720>: dequeue native buffer fail: No such device, buffer=0x0, handle=0x0

W Adreno-ES20: <core_glFinish:23>: GL_OUT_OF_MEMORY

Thanks

venkat

[David Seabolt]

It's been awhile since I looked at the code but I want to say it was because I was trying to release the back buffer after it had been released due to async issues. I hope that helps.

--
You received this message because you are subscribed to a topic in the Google Groups "android-ndk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-ndk/W5FTSeIA9QM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-ndk...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-ndk.
For more options, visit https://groups.google.com/d/optout.