Open
Bug 1832860
(webgpu-shader-error-stacks)
Opened 1 year ago
Updated 1 year ago
Add call stack information to shader creation errors in JS console
Categories
(Core :: Graphics: WebGPU, defect, P2)
Core
Graphics: WebGPU
Tracking
()
NEW
People
(Reporter: ErichDonGubler, Unassigned)
References
(Blocks 1 open bug)
Details
JS-native console
logging uses the call stack of currently running JS, but our current native usage of the [Console
API] [GPUDevice.createShaderModule
] doesn't emit this. This can be observed by viewing the attachment called desired-behavior-3-aggregated-callout.html
in bug 1826681 in Nightly.
We should see if we can preserve the calling context of createShaderModule
for presentation when presenting shader compilation messages.
Reporter | ||
Comment 1•1 year ago
|
||
:jimb and I think we should be able to do this using nsScriptErrorWithStack
, or something like it, and construct it after unconditionally saving a stack during the initial call to GPUDevice.createShaderModule
.
Reporter | ||
Updated•1 year ago
|
Priority: -- → P2
Reporter | ||
Updated•1 year ago
|
Severity: S2 → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•