Open Bug 1679425 Opened 4 years ago Updated 3 months ago

Crash in [@ shutdownhang | mozilla::TaskController::GetRunnableForMTTask | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread]

Categories

(Core :: SQLite and Embedded Database Bindings, defect, P3)

Unspecified
Windows
defect

Tracking

()

Tracking Status
thunderbird_esr91 + affected
firefox-esr78 --- unaffected
firefox83 + wontfix
firefox84 --- wontfix
firefox85 --- affected
firefox86 --- affected

People

(Reporter: aryx, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, Whiteboard: [tbird crash])

Crash Data

Signature existed before, crash volume seems to have increased with Firefox 83.0 (crash count for previous releases almost reached).

Crash report: https://crash-stats.mozilla.org/report/index/bde44598-bb3b-4293-850e-2451a0201126

MOZ_CRASH Reason: Shutdown hanging at step quit-application. Something is blocking the main-thread.

Top 10 frames of crashing thread:

0 ntdll.dll NtWaitForKeyedEvent 
1 ntdll.dll RtlSleepConditionVariableSRW 
2 kernel32.dll SleepConditionVariableSRW 
3 mozglue.dll mozilla::detail::ConditionVariableImpl::wait mozglue/misc/ConditionVariable_windows.cpp:50
4 xul.dll mozilla::TaskController::GetRunnableForMTTask xpcom/threads/TaskController.cpp:283
5 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1143
6 xul.dll nsThread::Shutdown xpcom/threads/nsThread.cpp:898
7 xul.dll mozilla::storage::Connection::shutdownAsyncThread storage/mozStorageConnection.cpp:1080
8 xul.dll mozilla::detail::RunnableMethodImpl< xpcom/threads/nsThreadUtils.h:1240
9 xul.dll mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:515

Crash signature existed for 81 and before but not for 82.

Is this a signature change and/or an increase in crash volume?

Flags: needinfo?(jstutte)
Crash Signature: [@ shutdownhang | mozilla::TaskController::GetRunnableForMTTask | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread] → [@ shutdownhang | mozilla::TaskController::GetRunnableForMTTask | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread] [@ shutdownhang | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread]
Flags: needinfo?(jstutte) → needinfo?(sgiesecke)

But very likely signatures will change soon once bug 1672369 landed entirely.

See Also: → 1672369

(In reply to Jens Stutte [:jstutte] from comment #4)

But very likely signatures will change soon once bug 1672369 landed entirely.

This isn't the quota manager/client shutdown hang, so I don't think this will have changed with that bug.

Adding two more Windows-specific signatures, which seem to be related.

Apparently, the behaviour in Nightly is differently, since we have almost no reports for Nightly. Maybe there's an assertion failure instead in Nightly?

Crash Signature: [@ shutdownhang | mozilla::TaskController::GetRunnableForMTTask | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread] [@ shutdownhang | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread] → [@ shutdownhang | mozilla::TaskController::GetRunnableForMTTask | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread] [@ shutdownhang | nsThread::Shutdown | mozilla::storage::Connection::shutdownAsyncThread] [@ shutdownhang | RtlAcqu…
Flags: needinfo?(sgiesecke)

(In reply to Simon Giesecke [:sg] [he/him] from comment #5)

Apparently, the behaviour in Nightly is differently, since we have almost no reports for Nightly. Maybe there's an assertion failure instead in Nightly?

I assume this is due to the fast shutdown being active on nightly, see bug 1606879 and children.

Severity: -- → S3
Priority: -- → P3

There's a bunch of underlying consumers of mozStorage all mashed together here (ex: NSS/SSL DataStorage, legacy LocalStorage), but the unifying factor is mozStorage's async thread shutdown call. Moving to Toolkit::Storage. Note that the common cause also does seem to be that code is still actively doing database stuff.

The actionable thing here would be to require all consumers of mozStorage to provide an explicit async shutdown blocker to better attribute errors, but in general it's also a question of doing crash-only shutdown in some cases. (Although not when privacy is involved.)

Component: Storage: StorageManager → Storage
Product: Core → Toolkit

Just had a couple crashes with "mozilla::TaskController::GetRunnableForMTTask", and started a new bug. Just an FYI.

bp-f1469a5c-4049-401a-bac7-ecd0c0211031 - #33 crash for Thunderbird 91.2.1

Whiteboard: [tbird crash]

The bug is linked to a topcrash signature, which matches the following criterion:

  • Top 20 desktop browser crashes on release

:mak, could you consider increasing the severity of this top-crash bug?

For more information, please visit auto_nag documentation.

Flags: needinfo?(mak)
Keywords: topcrash

Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.

For more information, please visit auto_nag documentation.

Keywords: topcrash
Flags: needinfo?(mak)

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

bp-f1469a5c-4049-401a-bac7-ecd0c0211031 - #33 crash for Thunderbird 91.2.1

#34 for Thunderbird 102.4.1

Product: Toolkit → Core
You need to log in before you can comment on or make changes to this bug.