Intermittent `MOZ_ASSERT_UNREACHABLE: unexpected to be called` in mozilla::webgpu::WebGPUParent::SwapChainPresent
Categories
(Core :: Graphics: WebGPU, defect, P2)
Tracking
()
People
(Reporter: intermittent-bug-filer, Assigned: sotaro)
References
Details
(Keywords: crash, intermittent-failure, intermittent-testcase, Whiteboard: [collect_confirm_failure])
Crash Data
Filed by: egubler [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=591977285&repo=try&task=BFFSUBhIQ9uX_COqDqQh7Q.0
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/BFFSUBhIQ9uX_COqDqQh7Q/runs/0/artifacts/public/logs/live_backing.log
Comment 2•2 months ago
|
||
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?
| Assignee | ||
Updated•2 months ago
|
| Comment hidden (Intermittent Failures Robot) |
Updated•1 month ago
|
Comment 4•1 month ago
|
||
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.
Comment 5•1 month ago
|
||
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.
Comment 6•1 month ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.
Description
•