Closed Bug 1643047 Opened 6 years ago Closed 4 years ago

Crash in [@ IPCError-browser | ShutDownKill | mozilla::BackgroundHangMonitor::NotifyActivity ]

Categories

(Core :: XPCOM, defect)

Unspecified
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: sg, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-5d6b45b1-43b4-47bf-a395-0b7550200603.

Top 10 frames of crashing thread:

0 ntdll.dll NtWaitForAlertByThreadId 
1 ntdll.dll RtlAcquireSRWLockExclusive 
2 xul.dll mozilla::BackgroundHangMonitor::NotifyActivity toolkit/components/backgroundhangmonitor/BackgroundHangMonitor.cpp:758
3 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1170
4 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:501
5 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
6 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:308
7 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
8 xul.dll nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
9 xul.dll nsAppShell::Run widget/windows/nsAppShell.cpp:430

At least with this signature, reports have started with Nightly build 20200509091423

Component: General → XPCOM
Product: Toolkit → Core

I noticed a couple of shutdown hangs with this signature on Sept 7th Nightlies. The hangs were caused by RtlSleepConditionVariableSRW.

Crash Signature: [@ IPCError-browser | ShutDownKill | RtlAcquireSRWLockExclusive | mozilla::BackgroundHangMonitor::NotifyActivity] → [@ IPCError-browser | ShutDownKill | RtlAcquireSRWLockExclusive | mozilla::BackgroundHangMonitor::NotifyActivity] [@ IPCError-browser | ShutDownKill | mozilla::BackgroundHangMonitor::NotifyActivity ]
Summary: Crash in [@ IPCError-browser | ShutDownKill | RtlAcquireSRWLockExclusive | mozilla::BackgroundHangMonitor::NotifyActivity] → Crash in [@ IPCError-browser | ShutDownKill | mozilla::BackgroundHangMonitor::NotifyActivity ]
Crash Signature: [@ IPCError-browser | ShutDownKill | RtlAcquireSRWLockExclusive | mozilla::BackgroundHangMonitor::NotifyActivity] [@ IPCError-browser | ShutDownKill | mozilla::BackgroundHangMonitor::NotifyActivity ] → [@ IPCError-browser | ShutDownKill | RtlAcquireSRWLockExclusive | mozilla::BackgroundHangMonitor::NotifyActivity] [@ IPCError-browser | ShutDownKill | mozilla::BackgroundHangMonitor::NotifyActivity ] [@ IPCError-browser | ShutDownKill | _tailMerge_d3dco…

Nika, do you know who might be the best person to look into this?

Flags: needinfo?(nika)

Maybe Doug could take a look? I think the hang monitor might be Nightly-only, in which case it isn't a huge issue. It doesn't look to be too common.

Flags: needinfo?(nika) → needinfo?(dothayer)

Yeah, BHR is Nightly-only. I am not too concerned about this, though it will be relevant if we ever want to enable BHR past Nightly.

Flags: needinfo?(dothayer)

Closing because no crashes reported for 12 weeks.

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