Crash in [@ shutdownhang | nsTHashtable<T>::s_HashKey | nsZipArchive::GetDataOffset]
Categories
(Core :: Networking: JAR, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr78 | --- | unaffected |
| firefox-esr91 | --- | affected |
| firefox91 | --- | wontfix |
| firefox92 | --- | wontfix |
| firefox93 | --- | wontfix |
People
(Reporter: aryx, Unassigned)
Details
(Keywords: crash, Whiteboard: [necko-triaged])
Crash Data
112 crash reports for the last month, all on Windows with 64-bit Firefox 90+ binaries.
Crash report: https://crash-stats.mozilla.org/report/index/6921c6ab-07b5-4bae-82b3-bbdb60210813
MOZ_CRASH Reason: Shutdown hanging at step quit-application. Something is blocking the main-thread.
Top 10 frames of crashing thread:
0 xul.dll static nsTHashtable<gfxGlyphExtents::HashEntry>::s_HashKey
1 xul.dll nsZipArchive::GetDataOffset modules/libjar/nsZipArchive.cpp:848
2 xul.dll nsZipArchive::GetData modules/libjar/nsZipArchive.cpp:865
3 xul.dll nsJAR::GetInputStreamWithSpec modules/libjar/nsJAR.cpp:280
4 xul.dll nsJAR::GetInputStream modules/libjar/nsJAR.cpp:255
5 xul.dll nsJARInputThunk::Init modules/libjar/nsJARChannel.cpp:113
6 xul.dll nsJARChannel::CreateJarInput modules/libjar/nsJARChannel.cpp:280
7 xul.dll nsJARChannel::Open modules/libjar/nsJARChannel.cpp:1036
8 xul.dll NS_MaybeOpenChannelUsingOpen netwerk/base/nsNetUtil.cpp:2582
9 xul.dll mozJSComponentLoader::ObjectForLocation js/xpconnect/loader/mozJSComponentLoader.cpp:806
Comment 1•5 years ago
|
||
The top frame here (static nsTHashtable<gfxGlyphExtents::HashEntry>::s_HashKey(void const*)) doesn't seem to make any sense in the context of the rest of the stack; why would nsZipArchive::GetDataOffset be doing anything related to hashtable entries??
| Reporter | ||
Updated•5 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.
For more information, please visit auto_nag documentation.
Comment 3•4 years ago
|
||
Slightly different signature, but actually the same on a different platform.
Updated•2 years ago
|
Updated•5 months ago
|
Description
•