Crash in [@ nsRefreshDriver::Tick]
Categories
(Core :: Graphics: WebGPU, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox75 | --- | unaffected |
firefox76 | --- | unaffected |
firefox77 | + | fixed |
People
(Reporter: pascalc, Assigned: kvark)
References
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
This bug is for crash report bp-9c64052c-c782-4fd7-baea-f42460200424.
Top 10 frames of crashing thread:
0 xul.dll nsRefreshDriver::Tick layout/base/nsRefreshDriver.cpp:2264
1 xul.dll mozilla::RefreshDriverTimer::TickRefreshDrivers layout/base/nsRefreshDriver.cpp:351
2 xul.dll mozilla::RefreshDriverTimer::Tick layout/base/nsRefreshDriver.cpp:368
3 xul.dll mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::TickRefreshDriver layout/base/nsRefreshDriver.cpp:746
4 xul.dll mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::NotifyVsync layout/base/nsRefreshDriver.cpp:645
5 xul.dll mozilla::layout::VsyncChild::RecvNotify layout/ipc/VsyncChild.cpp:55
6 xul.dll mozilla::layout::PVsyncChild::OnMessageReceived ipc/ipdl/PVsyncChild.cpp:187
7 xul.dll mozilla::ipc::PBackgroundChild::OnMessageReceived ipc/ipdl/PBackgroundChild.cpp:5970
8 xul.dll mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2110
9 xul.dll mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1989
We went from a couple of crashes a day to 50 crashes since yesterday. Most of the crashes are in build id 20200423145559 and some user comments in crash reports say that they tried the demos on https://hacks.mozilla.org/2020/04/experimental-webgpu-in-firefox/
Maybe this is not a regression but more attention given by yesterday's blog post to an existing crashing code path.
Comment 1•5 years ago
|
||
Probably better if GFX triage this if it's possibly related to webgpu in any way.
Assignee | ||
Comment 2•5 years ago
|
||
Yeah, I've seen this myself once. A bit confusing about how this relates to WebGPU, given that nothing in the call stack suggests that. Will look into this anyway.
Assignee | ||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Changing the priority to p2 as the bug is tracked by a release manager for the current nightly.
See What Do You Triage for more information
Assignee | ||
Comment 4•5 years ago
|
||
Comment 6•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 7•5 years ago
|
||
Is there anything actionable by QA? if yes, could you please provide STR?
Thank you in advance!
Reporter | ||
Comment 8•5 years ago
|
||
Nothing to do for QA, we don't have crashes on Beta with this signature.
Description
•