Closed Bug 844280 Opened 8 years ago Closed 4 years ago

"Assertion failure: gl->IsFramebufferComplete(fb)"

Categories

(Core :: Canvas: WebGL, defect)

x86_64
macOS
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jruderman, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: assertion, regression, testcase, Whiteboard: [gfx-noted] webgl-internal)

Attachments

(2 files)

Assertion failure: gl->IsFramebufferComplete(fb), at gfx/gl/GLScreenBuffer.cpp:560

I'm guessing this is a regression from bug 716859.
Attached file stack
Component: SVG → Canvas: WebGL
Ok, this looks simple enough. It looks like we aren't handling too-large canvases properly.
Whiteboard: webgl-internal
Is this bug still valid?
Flags: needinfo?(jruderman)
Whiteboard: webgl-internal → [gfx-noted] webgl-internal
On Win7 debug, this intermittently hits [@ mozilla::gl::GLContext::AfterGLCall(char const *)] crashes on Try that look a lot like bug 1402553 (known OOM-like behavior). Otherwise, it looks green.
https://treeherder.mozilla.org/logviewer.html#?job_id=142941461&repo=try

I'm inclined to just mark this WFM and land the test skipped on Win7 debug.
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(jruderman) → in-testsuite+
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.