Closed Bug 2071219 Opened 2 months ago Closed 1 month ago

Intermittent `MOZ_ASSERT_UNREACHABLE: unexpected to be called` in mozilla::webgpu::WebGPUParent::SwapChainPresent

Categories

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

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Assigned: sotaro)

References

Details

(Keywords: crash, intermittent-failure, intermittent-testcase, Whiteboard: [collect_confirm_failure])

Crash Data

CC :sotaro.

Severity: -- → S3

This appears to be happening because https://hg-edge.mozilla.org/try/file/70dcf5c29bdda0b953dc7ed14eb447377e17017a/dom/webgpu/ipc/WebGPUParent.cpp#l1195 is being reached, that is, the ID for the swapchain texture to present is being removed from the list. This seems like a lifecycle issue, maybe?

Flags: needinfo?(sotaro.ikeda.g)
Assignee: nobody → sotaro.ikeda.g
Flags: needinfo?(sotaro.ikeda.g)
Priority: -- → P2

The assertion in question may need to be changed to an NS_WARNING as was done for some others in https://phabricator.services.mozilla.com/D318640. Some of these are reachable when the application requests an invalid swap chain (GPUCanvasContext) configuration.

See Also: → 2059002

In yesterday's (2026-09-21) WebGPU team sync. meeting, :jimb suspected that this may have been an issue with SwapChainPresent being called for a texture that failed initialization.

Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.