Closed Bug 784277 Opened 7 years ago Closed Last year
ABORT: Framebuffer not complete -- error 0x8cd6 on JB/gonk/grouper nexus-7
On nexus-7 with JB android (tegra) I see this error when unlocking screen after first startup: I/Gecko (13104): [Parent 13104] ###!!! ABORT: Framebuffer not complete -- error 0x8cd6, mFBOTextureTarget 0xde1, aRect.width 1585, aRect.height 2497: file B2G/gecko/gfx/layers/opengl/LayerManagerOGL.cpp, line 1200 Default framebuffer depth is 32bpp. Also have seen same problem on raspberry pi with LinuxGL backend
It crashes 8/10, also it goes through this path before crash: http://mxr.mozilla.org/mozilla-central/source/gfx/layers/opengl/LayerManagerOGL.cpp#1145
I'm not quite understanding -- what are running on the Nexus 7? Gonk built as... an android app? Running by itself directly?
0x8cd6 is FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT; sounds like we're missing something, perhaps a color attachment if we're doing a copyteximage?
The framebuffer rect's height (2497) likely exceeds the maximum texture size (probably 2048), so texture creation will fail, leading to an incomplete framebuffer. See Bug 746730, Comment 9, for a possible solution.
(In reply to Vladimir Vukicevic [:vlad] [:vladv] from comment #2) > I'm not quite understanding -- what are running on the Nexus 7? Gonk built > as... an android app? Running by itself directly? It is FirefoxOS b2g, ported on JB android, running itself directly (like normal b2g)
(In reply to Ali Juma [:ajuma] from comment #4) > The framebuffer rect's height (2497) likely exceeds the maximum texture size Yep, that seems like a real problem, because Nexus-7 is 7" tablet and has by default bigger screen which is leading bigger sizes for intermediate buffers
It might be fixed in 19.0 by the patch of bug 827170. Does it still happen in B2G/18.0?
Severity: normal → critical
don't know, haven't touched nx7 device and related b2g build
Closing as we are not working on Firefox OS anymore.
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.