Open Bug 1594056 Opened 2 years ago Updated 12 days ago

Crash in [@ shutdownhang | memset | je_free | mozilla::detail::HashTable<T>::destroyTable | mozilla::scache::StartupCache::~StartupCache]

Categories

(Toolkit :: Startup and Profile System, defect, P2)

71 Branch
All
Windows 7
defect

Tracking

()

Tracking Status
firefox-esr68 --- unaffected
firefox70 --- unaffected
firefox71 --- wontfix
firefox72 --- fix-optional

People

(Reporter: philipp, Unassigned)

References

(Regression)

Details

(Keywords: crash, regression)

Crash Data

This bug is for crash report bp-52ad50b2-90b7-478b-8dd5-0ee1c0191105.

Top 10 frames of crashing thread:

0 vcruntime140.dll memset f:\dd\vctools\crt\vcruntime\src\string\i386\memset.asm:86
1 mozglue.dll je_free memory/build/malloc_decls.h:54
2 xul.dll static void mozilla::detail::HashTable<mozilla::HashMapEntry<nsTString<char>, mozilla::scache::StartupCacheEntry>, mozilla::HashMap<nsTString<char>, mozilla::scache::StartupCacheEntry, mozilla::scache::nsCStringHasher, mozilla::MallocAllocPolicy>::MapHashPolicy, mozilla::MallocAllocPolicy>::destroyTable mfbt/HashTable.h:1647
3 xul.dll void mozilla::scache::StartupCache::~StartupCache startupcache/StartupCache.cpp:155
4 xul.dll unsigned long PipUIContext::Release xpcom/threads/nsThreadUtils.cpp:39
5 xul.dll mozilla::ShutdownXPCOM xpcom/build/XPCOMInit.cpp:628
6 xul.dll void ScopedXPCOMStartup::~ScopedXPCOMStartup toolkit/xre/nsAppRunner.cpp:1246
7 xul.dll int XREMain::XRE_main toolkit/xre/nsAppRunner.cpp:4761
8 xul.dll XRE_main toolkit/xre/nsAppRunner.cpp:4815
9 xul.dll int mozilla::BootstrapImpl::XRE_main toolkit/xre/Bootstrap.cpp:45

there are a number of shutdown hang signatures regressing in firefox 71 from windows, apparently related to the changes in bug 1550108.

so far there aren't any useful correlations or comments that might provide some better understanding of the circumstances of those crashes yet though.

Flags: needinfo?(dothayer)

So, am I understanding these crash reports correctly that somehow the destruction of the table in the StartupCache destructor is taking a long time, causing the watchdog thread to time out and MOZ_CRASH us? I'm not sure if I understand how it says the crashing thread is the main thread but with a reason of MOZ_CRASH("Shutdown too long, probably frozen, causing a crash.")

Flags: needinfo?(dothayer)

The priority flag is not set for this bug.
:mossop, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dtownsend)

We have shipped our last beta for 71, I am setting the status as fix-optional for 71 in case there is a safe uplift possible for these crashes in a potential dot release as a ride-along.

Doesn't look like this is happening terribly often, but please up the priority if I'm misreading.

Flags: needinfo?(dtownsend)
Priority: -- → P2
Crash Signature: | PR_MD_WAIT_CV | PR_JoinThread | mozilla::scache::StartupCache::~StartupCache] [@ shutdownhang | memset | je_free | mozilla::scache::StartupCache::~StartupCache] [@ shutdownhang | mozilla::scache::StartupCache::~StartupCache] → | PR_MD_WAIT_CV | PR_JoinThread | mozilla::scache::StartupCache::~StartupCache] [@ shutdownhang | memset | je_free | mozilla::scache::StartupCache::~StartupCache] [@ shutdownhang | mozilla::scache::StartupCache::~StartupCache] [@ shutdownhang | memset…
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.