Open Bug 1612854 Opened 9 months ago Updated 5 months ago

Crash in [@ NtYieldExecution]


(Core :: XPCOM, defect)

Windows 10
Not set



Tracking Status
firefox74 --- affected
firefox79 --- affected


(Reporter: pascalc, Unassigned)


(Keywords: crash)

Crash Data

This bug is for crash report bp-d69aecd5-a1dc-4416-98a9-0e2ce0200203.

Top 10 frames of crashing thread:

0 ntdll.dll NtYieldExecution 
1 user32.dll PeekMessageW 
2 xul.dll SingleNativeEventPump::OnProcessNextEvent widget/windows/nsAppShell.cpp:140
3 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1124
4 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486
5 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
6 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/
7 xul.dll MessageLoop::Run ipc/chromium/src/base/
8 xul.dll nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
9 xul.dll nsAppShell::Run widget/windows/nsAppShell.cpp:406

We have a handfull of crashes with this signature every week on Nightly.

It looks like we're spinning the event loop in almost all of these crashes. I'm not really sure if we can do anything more with this information.

Component: General → XPCOM


My Firefox Nightly has been crash happy as of recently:

Submitted Crash Reports
Report ID Date Submitted
bp-7071e8f8-3a1f-4564-8713-c826f0200603 6/3/2020, 12:57
bp-6d95a5d8-bfe2-4169-972d-9fd1a0200603 6/3/2020, 12:57
bp-48b48d26-b16a-44ae-9fc8-58e550200603 6/3/2020, 12:57
bp-2bf2eea4-7d95-4fe1-b470-7be550200603 6/3/2020, 12:49
bp-e364885d-efc5-40de-b94d-a67780200603 6/3/2020, 12:49
bp-85a3b9bc-6177-499e-a8fe-c28ff0200603 6/3/2020, 12:49
bp-630d4ec3-cf40-4282-ad1a-2de110200603 6/3/2020, 08:22
bp-0ac0fdcd-d1d9-4ba3-a001-b370f0200603 6/3/2020, 08:22
bp-65984e36-dca4-4a77-b3b1-30e070200603 6/3/2020, 08:22

Updating flag FWIW.


You need to log in before you can comment on or make changes to this bug.