ID: bp-50a35544-6419-4714-8abe-7003b0191009

Had this crash on my Thunderbird when I turned PC on in the morning.

(In reply to Worcester12345 from comment #0)

ID: 50a35544-6419-4714-8abe-7003b0191009

Had this crash on my Thunderbird when I turned PC on in the morning.

115 seconds uptime, so confirmed this is a startup crash.

Did you have problems clicking the "Thunderbird" link at https://crash-stats.mozilla.org/report/index/50a35544-6419-4714-8abe-7003b0191009#tab-bugzilla ??

(In reply to Wayne Mery (:wsmwk) from comment #1)

(In reply to Worcester12345 from comment #0)

ID: 50a35544-6419-4714-8abe-7003b0191009

Had this crash on my Thunderbird when I turned PC on in the morning.

115 seconds uptime, so confirmed this is a startup crash.

Did you have problems clicking the "Thunderbird" link at https://crash-stats.mozilla.org/report/index/50a35544-6419-4714-8abe-7003b0191009#tab-bugzilla ??

No, that link was how I filed this bug.

ZING! Got it again.

bp-7deb65e6-bf04-4a4e-bc02-d28230191021
Signature: shutdownhang | nsThread::Shutdown | nsSound::Observe

(In reply to Worcester12345 from comment #4)

ZING! Got it again. bp-7deb65e6-bf04-4a4e-bc02-d28230191021 201 seconds of uptime

And what were you doing when it crashed?

I don't recall now, but it seems a lot of crashes happen during or after a search. I also see crashes after leaving PC on overnight, and show up to a crash the next morning.

How reproducible is this?
Does it go away if you disable McAfee?

I'd prefer not to disable the anti-virus. This is a production environment machine.

Ben, what do you make of this?

#15 crash for 68.4.1. Some of the crashes have non-microsoft AV installed, but the majority do not.

Oddly, none of the crashes happens before 71 seconds of uptime. For example bp-bc5d277d-5d8e-4212-84dc-f1ea40200114
0 ntdll.dll NtWaitForAlertByThreadId context
1 ntdll.dll RtlSleepConditionVariableSRW cfi
2 kernelbase.dll SleepConditionVariableSRW cfi
3 mozglue.dll mozilla::detail::ConditionVariableImpl::wait(mozilla::detail::MutexImpl&) mozglue/misc/ConditionVariable_windows.cpp:50 cfi
4 xul.dll mozilla::ThreadEventQueue<mozilla::PrioritizedEventQueue<mozilla::EventQueue> >::GetEvent(bool, mozilla::EventQueuePriority*) xpcom/threads/ThreadEventQueue.cpp:149 cfi
5 xul.dll nsThread::ProcessNextEvent(bool, bool*) xpcom/threads/nsThread.cpp:1108 cfi
6 xul.dll NS_ProcessNextEvent(nsIThread*, bool) xpcom/threads/nsThreadUtils.cpp:486 cfi
7 xul.dll nsThread::Shutdown() xpcom/threads/nsThread.cpp:881 cfi
8 xul.dll nsSound::Observe(nsISupports*, char const*, char16_t const*) widget/windows/nsSound.cpp:227 cfi
9 xul.dll nsObserverList::NotifyObservers(nsISupports*, char const*, char16_t const*) xpcom/ds/nsObserverList.cpp:66 cfi
10 xul.dll nsObserverService::NotifyObservers(nsISupports*, char const*, char16_t const*) xpcom/ds/nsObserverService.cpp:295 cfi

Increased to #10 crash

Magnus, what do you make of this?

MOZ_CRASH(Shutdown too long, probably frozen, causing a crash.) Looked at bp-d626e5f-fc84-47b0-8a82-568fa02020528

So the internals will time out after some time, then force a crash.

Anyway, maybe the same as whatever we have/had for starting up with no 3pane, and then close after?

crash rate for beta 80 and 81 is zero https://crash-stats.mozilla.org/signature/?release_channel=beta&signature=shutdownhang%20%7C%20nsThread%3A%3AShutdown%20%7C%20nsSound%3A%3AObserve&date=%3E%3D2020-03-10T12%3A32%3A00.000Z&date=%3C2020-09-10T12%3A32%3A00.000Z#graphs ... so something fixed beta, or the signature changed

but version 78 has not improved https://crash-stats.mozilla.org/signature/?version=78.1.0&version=78.1.1&version=78.0&version=78.0.1&version=78.1.2&version=78.2.0&version=78.2.1&version=78.0.2&signature=shutdownhang%20%7C%20nsThread%3A%3AShutdown%20%7C%20nsSound%3A%3AObserve&date=%3E%3D2020-06-10T12%3A33%3A00.000Z&date=%3C2020-09-10T12%3A33%3A00.000Z#graphs

Judging by the last 6 months the crash rate has not changed going from v68 to v78

(In reply to Magnus Melin [:mkmelin] from comment #11)

Anyway, maybe the same as whatever we have/had for starting up with no 3pane, and then close after?

I'm not familiar with that. Is there a bug number?

Unfortunately I've forgot what I meant there.

There are no version 91 crashes reported for this signature, so closing this report.

Thanks. If any "reports for this signature" start coming in again, will this be reopened?