Crash in [@ mozilla::EventTargetChainItem::GetEventTargetParent]
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox70 | --- | affected |
People
(Reporter: philipp, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-f6692cd7-0c2d-4abd-b248-d01d70191102.
Top 10 frames of crashing thread:
0 xul.dll void mozilla::EventTargetChainItem::GetEventTargetParent dom/events/EventDispatcher.cpp:421
1 xul.dll mozilla::EventDispatcher::Dispatch dom/events/EventDispatcher.cpp:962
2 xul.dll mozilla::EventDispatcher::DispatchDOMEvent dom/events/EventDispatcher.cpp
3 xul.dll nsINode::DispatchEvent dom/base/nsINode.cpp:1061
4 xul.dll mozilla::AsyncEventDispatcher::Run dom/events/AsyncEventDispatcher.cpp:69
5 xul.dll mozilla::SchedulerGroup::Runnable::Run xpcom/threads/SchedulerGroup.cpp:295
6 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1225
7 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486
8 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:88
9 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:308
this crash signature is showing up with increased frequency in the Firefox 70.0.1 release. it seems to be specific to AMD cpus "family 23 model 1" (Ryzen 7), which is the first time for this particular cpu family afaik.
Comment 1•4 years ago
|
||
Currently this signature is #14 overall on the 70.0.1 release.
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Unfortunately the crash reports don't seem to reveal where the issue is.
The code where the crash is happening hasn't changed recently.
nsThread::ProcessNextEvent
has changed a little. Could this be related to some fission work? As a reminder, this issue was reported for the 70 release.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Crash volume in 71 was very low.
Comment 6•2 years ago
|
||
Since the crash volume is low (less than 5 per week), the severity is downgraded to S3
. Feel free to change it back if you think the bug is still critical.
For more information, please visit auto_nag documentation.
Description
•