Closed Bug 2083506 Opened 1 month ago Closed 28 days ago

Update wgpu to upstream e084b66aa (2026-10-18)

Categories

(Core :: Graphics: WebGPU, task, P1)

task

Tracking

()

RESOLVED FIXED
160 Branch
Tracking Status
firefox160 --- fixed

People

(Reporter: jimb, Assigned: jimb)

References

(Blocks 1 open bug)

Details

Attachments

(1 external file)

What it says on the tin.

Assignee: nobody → jimb
Blocks: 2011051
Priority: -- → P1

Import a new version of wgpu_core, naga and related crates, and
adapt gfx/wgpu_bindings and dom/webgpu/ipc to API changes.

In the newly vendored version of the wgpu crates,
wgpu_core_remote::Global::buffer_get_mapped_range returns a
wgpu_core::resource::BufferMapping value that ensures the pointer to the
mapped memory remains valid until it is dropped. In the C++ bindings, introduce
a new MappedRangeGuard type for use by WebGPUParent that owns the mapped
range and releases the BufferMapping when it is dropped. Change all callers of
wgpu_server_buffer_get_mapped_range to use MappedRangeGuard instead.

Since MappedRangeGuard causes buffer unmapping and destruction to block, take
care not to hold a MappedRangeGuard across any such operation, or any call
that might perform one, to avoid deadlock.

Added missing explicit keyword on MappedRangeGuard constructor.
try push

It seems like we have new instances of bug 1840858: mac debug now behaves like mac release.

Updated test expectations for backlog.
try push

queued for landing

Pushed by jblandy@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/5e1c2c4a78b4 https://hg.mozilla.org/integration/autoland/rev/2ef43fb5d052 Update wgpu to upstream e084b66aa (2026-10-18) r=webgpu-reviewers,supply-chain-reviewers,teoxoy
Status: NEW → RESOLVED
Closed: 28 days ago
Resolution: --- → FIXED
Target Milestone: --- → 160 Branch
QA Whiteboard: [qa-triage-done-c161/b160]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: