1632707 - Crash in [@ mozilla::webgpu::PresentCallback]

Status: RESOLVED WORKSFORME

(Core :: Graphics: WebGPU, defect, P3)

Description

[Andrew McCreight [:mccr8]]

This bug is for crash report bp-46bda1c2-c38c-4967-8524-b429f0200423.

Top 10 frames of crashing thread:

0 XUL mozilla::webgpu::PresentCallback dom/webgpu/ipc/WebGPUParent.cpp:582
1 XUL wgpu_core::device::fire_map_callbacks gfx/wgpu/wgpu-core/src/device/mod.rs
2 XUL wgpu_core::device::<impl wgpu_core::hub::Global<G>>::queue_submit gfx/wgpu/wgpu-core/src/device/mod.rs:1564
3 XUL mozilla::webgpu::WebGPUParent::RecvSwapChainPresent dom/webgpu/ipc/WebGPUParent.cpp:667
4 XUL mozilla::webgpu::PWebGPUParent::OnMessageReceived ipc/ipdl/PWebGPUParent.cpp:2297
5 XUL mozilla::layers::PCompositorManagerParent::OnMessageReceived ipc/ipdl/PCompositorManagerParent.cpp:197
6 XUL mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2186
7 XUL mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1989
8 XUL <name omitted> ipc/chromium/src/base/message_pump_default.cc:35
9 XUL MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290

Null deref. Only 2 crashes, from a single installation, but maybe it'll still be of interest.

Comment 1

[Dzmitry Malyshau [:kvark]]

Looked at this briefly, not sure what conditions would lead to the null access violation.
The data has a refcount added before the callback, and released at the end of it, so it shouldn't be NULL.
The data->mTextureHost is permanently associated with data and accessed all the time.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.