The default bug view has changed. See this FAQ.

WebGL crash [@mozilla::gl::GLContext::fFramebufferRenderbuffer]

RESOLVED FIXED

Status

()

Core
Canvas: WebGL
--
critical
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: posidron, Unassigned)

Tracking

(Blocks: 1 bug, {crash, testcase})

Trunk
x86
Windows 7
crash, testcase
Points:
---

Firefox Tracking Flags

(status1.9.2 unaffected, status1.9.1 unaffected)

Details

(crash signature)

Attachments

(2 attachments)

(Reporter)

Description

7 years ago
Created attachment 486323 [details]
testcase

Tested inside VMWare Fusion.

VMware SVGA 3D (Microsoft Corporation - WDDM)
Driver version: 7.14.1.42
(Reporter)

Comment 1

7 years ago
Created attachment 486324 [details]
callstack
This callstack looks like a bug in VMWare's OpenGL implementation. It internally converts a number to a string and that crashes. We can't do anything about it.

Incidentally, our framebufferRenderbuffer implementation is undergoing a rewrite, but that won't make a difference because we can't avoid calling glFramebufferRenderbuffer.
Ah, it is still possible that we are bitten by GL asynchronousness making the stack trace irrelevant. If you want to rule that possibility out, grab a debug build of firefox and run with

   MOZ_GL_DEBUG=1 firefox

i.e. define the MOZ_GL_DEBUG environment variable to anything.
status1.9.1: --- → unaffected
status1.9.2: --- → unaffected
Keywords: crash, testcase
(Reporter)

Updated

6 years ago
Blocks: 658170
(Assignee)

Updated

6 years ago
Crash Signature: [@mozilla::gl::GLContext::fFramebufferRenderbuffer]

Updated

5 years ago
QA Contact: canvas.webgl → bjacob
This is fixed since we started blacklisting other vendors than AMD/NVIDIA/Intel (so, all virtualization thingy^Wenvironments)
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.