Open
Bug 1336835
Opened 9 years ago
Updated 3 years ago
WebGL printed diagnostics should come with a JS/Wasm callstack.
Categories
(Core :: Graphics: CanvasWebGL, enhancement, P3)
Tracking
()
REOPENED
People
(Reporter: jujjyl, Unassigned)
Details
(Whiteboard: gfx-noted)
When WebGL generates a GL error or a performance warning or anything else to page console, ghese reports do not have a callstack that the user could trace to identify what is generating the issue. Sometimes that makes it extremely hard to diagnose where a WebGL diagnostic report is coming from, especially on huge codebases that one did not write themselves.
It would be good to systematically print out callstacks for all WebGL errors/warnings/performance reports.
|
||
Updated•9 years ago
|
Priority: -- → P3
Whiteboard: gfx-noted
|
||
Comment 1•7 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
|
||
Updated•7 years ago
|
Status: RESOLVED → REOPENED
Resolution: INACTIVE → ---
|
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•