Closed
Bug 607593
Opened 15 years ago
Closed 14 years ago
WebGL crash [@mozilla::gl::GLContext::fFramebufferRenderbuffer]
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| status1.9.2 | --- | unaffected |
| status1.9.1 | --- | unaffected |
People
(Reporter: posidron, Unassigned)
Details
(Keywords: crash, testcase)
Crash Data
Attachments
(2 files)
Tested inside VMWare Fusion.
VMware SVGA 3D (Microsoft Corporation - WDDM)
Driver version: 7.14.1.42
|
Reporter | |
Comment 1•15 years ago
|
||
|
||
Comment 2•15 years ago
|
||
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.
|
|
||
Comment 3•15 years ago
|
||
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.
|
||
Updated•15 years ago
|
|
Assignee | |
Updated•15 years ago
|
Crash Signature: [@mozilla::gl::GLContext::fFramebufferRenderbuffer]
|
||
Updated•14 years ago
|
QA Contact: canvas.webgl → bjacob
|
|
||
Comment 4•14 years ago
|
||
This is fixed since we started blacklisting other vendors than AMD/NVIDIA/Intel (so, all virtualization thingy^Wenvironments)
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•