[webgpu] Insta crash on https://webgpu.github.io/webgpu-samples/samples/A-buffer
Categories
(Core :: Graphics: WebGPU, defect, P2)
Tracking
()
People
(Reporter: mayankleoboy1, Assigned: ErichDonGubler)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Crash Data
Attachments
(1 file)
44.35 KB,
text/plain
|
Details |
Go to https://webgpu.github.io/webgpu-samples/samples/A-buffer
Insta crash
I always get 2 crash reports from this
https://crash-stats.mozilla.org/report/index/dbef60f2-7c7b-42c2-a70d-ec6240231024
https://crash-stats.mozilla.org/report/index/f993fa9c-76c7-447a-ae1a-88d1a0231024
Reporter | ||
Comment 1•1 year ago
|
||
Reporter | ||
Comment 2•1 year ago
|
||
Bug 1831120: style(webgpu): add space b/w GPUBuffer.{unmap,destroy}
to match spec. r=webgpu-reviewers,webidl,saschanaz,jimb
Differential Revision: https://phabricator.services.mozilla.com/D177056
Reporter | ||
Updated•1 year ago
|
Reporter | ||
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Set release status flags based on info from the regressing bug 1831120
Assignee | ||
Updated•1 year ago
|
Comment 4•1 year ago
|
||
:ErichDonGubler, since you are the author of the regressor, bug 1831120, could you take a look?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Assignee | ||
Comment 5•1 year ago
|
||
I will investigate this as I find bandwidth to do so over the next couple of weeks. I suspect that the bug marked as the regressor is not actually the regressor (adding readonly attribute
and additional spacing in IDL likely has nothing to do with this), but rather something else that has unblocked logic that was stopping this bug from being observed before.
Assignee | ||
Updated•1 year ago
|
Reporter | ||
Comment 6•1 year ago
|
||
FWIW, I dont get the crash on the latest Nightly.
The fix is bug 1856371.
:ErichDonGubler: feel free to close this bug
Reporter | ||
Comment 7•1 year ago
|
||
It repros here now: https://toji.github.io/webgpu-clustered-shading/
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 8•1 year ago
|
||
Mayank: I'm confused. Is that the same crashing issue? Or does your other statement about closing this bug apply still?
Reporter | ||
Comment 9•1 year ago
|
||
Lets close this bug as the original link doesnt crash anymore.
The crash signatures from the demo in comment #7 has changed now (maybe because of bug 1861751). The new signatures are captured in other bugs i have filed (bug 1863107).
Updated•1 year ago
|
Updated•1 year ago
|
Reproducible on a 2023-10-24 Nightly build on Windows 10.
Verified as fixed on Firefox 121.0b4 and Nightly 122.0a1 on Windows 10, Ubuntu 22, macOS 12.
Description
•