Update WGPU to upstream (week of 2024-03-26)
Categories
(Core :: Graphics: WebGPU, task, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox126 | --- | fixed |
People
(Reporter: ErichDonGubler, Assigned: ErichDonGubler)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
| Assignee | ||
Comment 1•2 years ago
|
||
I'll take on this one, since :teoxoy is out.
| Assignee | ||
Comment 2•2 years ago
|
||
| Assignee | ||
Comment 3•2 years ago
|
||
Comment 5•2 years ago
|
||
Backed out 2 changesets (Bug 1887909) for causing failures in test_command_buffer_creation.html CLOSED TREE
Log: https://treeherder.mozilla.org/logviewer?job_id=452864938&repo=autoland&lineNumber=1896
Backout: https://hg.mozilla.org/integration/autoland/rev/d87381ca434918941fe3670ad182962d1933afb0
Comment 7•2 years ago
•
|
||
In the logs, dom/webgpu/mochitest/test_command_buffer_creation.html times out. This is because the mochitest that ran immediately before it, dom/webgpu/mochitest/test_buffer_mapping_invalid_device.html, has hung the GPU process trying to clean up device resources.
Specifically, wgpu_core::device::Device::maintain takes a &SnatchGuard argument, meaning that its caller must have a read guard on the device's snatch lock. However, mantain calls Device::release_gpu_resources, which calls Buffer::destroy, which tries to acquire a write guard on the snatch lock. Probably a similar problem would occur with Texture::destroy.
Comment 8•2 years ago
|
||
Filed upstream: https://github.com/gfx-rs/wgpu/issues/5471
Updated•2 years ago
|
| Assignee | ||
Comment 9•2 years ago
|
||
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/3ae3d83aae40
https://hg.mozilla.org/mozilla-central/rev/f6e62f23a6dc
https://hg.mozilla.org/mozilla-central/rev/4fbd7bf93c96
Description
•