Crash in [@ IPCError-browser | ShutDownKill | hashglobe::hash_map::HashMap<T>::clear<T>]
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Tracking
()
People
(Reporter: mccr8, Unassigned)
References
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-23dbaa5d-d06c-467e-96d7-14d1b0200206.
Top 10 frames of crashing thread:
0 xul.dll hashglobe::hash_map::HashMap<style::gecko_string_cache::Atom, smallvec::SmallVec<[style::stylist::Rule; 1]>, core::hash::BuildHasherDefault<style::selector_map::PrecomputedHasher>>::clear<style::gecko_string_cache::Atom, smallvec::SmallVec<[style::stylist::Rule; 1]>, core::hash::BuildHasherDefault<style::selector_map::PrecomputedHasher>> servo/components/hashglobe/src/hash_map.rs:1079
1 xul.dll style::stylist::GenericElementAndPseudoRules<style::selector_map::SelectorMap<style::stylist::Rule>>::clear servo/components/style/stylist.rs:1705
2 xul.dll style::stylist::CascadeData::clear_cascade_data servo/components/style/stylist.rs:2241
3 xul.dll style::stylist::CascadeData::clear servo/components/style/stylist.rs:2259
4 xul.dll style::stylist::CascadeData::rebuild<style::gecko::data::GeckoStyleSheet> servo/components/style/stylist.rs:1844
5 xul.dll geckoservo::glue::Servo_StyleSet_FlushStyleSheets servo/ports/geckolib/glue.rs:1900
6 xul.dll mozilla::ServoStyleSet::UpdateStylist layout/style/ServoStyleSet.cpp:1128
7 xul.dll mozilla::ServoStyleSet::ShellDetachedFromDocument layout/style/ServoStyleSet.cpp:133
8 xul.dll mozilla::dom::Document::DeletePresShell dom/base/Document.cpp:6311
9 xul.dll mozilla::PresShell::Destroy layout/base/PresShell.cpp:1333
This signature is one of the more common ones, at least in the Nightly I looked at. In the crashes I skimmed, it was clearing Stylo data while destroying a pres shell.
Comment 1•5 years ago
|
||
Does the signature mean this is a shutdown hang? Or something else?
Reporter | ||
Comment 2•5 years ago
|
||
Yes, I think that's what it means. Or at least, a hang while the process is shutting down.
Comment 3•5 years ago
|
||
Yes, these aren't crashes. They're snapshots of content processes that were told to shut down but didn't succeed within a minute. When this happens we take a minidump of the content process, kill it and then submit the crash report. Note the mozilla::dom::BrowserChild::RecvDestroy()
frame on the stack.
Comment 5•5 years ago
|
||
I found another signature, all the crashes from the past six months have been reprocessed so this should now cover pretty much all of them.
Comment 6•5 years ago
|
||
Calling this P3, since it's presumably not an especially user-visible issue, given that we eventually clean up the hanging process.
Reporter | ||
Updated•5 years ago
|
Comment 7•5 years ago
|
||
This is showing up very high in the Nightly crash stats. Is there something we can do to improve the situation here?
Reporter | ||
Comment 8•5 years ago
•
|
||
Could we do something like not destroy this style data if we're shutting down? It'll be a little tricky because we do need to destroy it in debug builds for leak checking purposes. The stacks I've seen are inside mozilla::dom::BrowserChild::RecvDestroy() so it should be possible to detect.
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 9•5 years ago
|
||
I added two more signatures that look like the same issue (synchronously destroying style data during shutdown).
Comment 10•5 years ago
|
||
Bugbug thinks this bug is a regression, but please revert this change in case of error.
Reporter | ||
Updated•5 years ago
|
Comment 11•5 years ago
|
||
Added a couple more signatures. We also have a corresponding shutdownhang entry (bug 1625835).
Updated•5 years ago
|
Comment 13•4 years ago
|
||
Added two more signatures.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 15•3 years ago
|
||
¡Hola y'all!
https://crash-stats.mozilla.org/report/index/19c64efd-1293-44a7-83ff-440370210524#tab-details bite me on 90.
Please let me know if there's anything you might need from the profile or device.
¡Gracias!
Alex
Updated•3 years ago
|
Comment 16•3 years ago
|
||
Closing because no crashes reported for 12 weeks.
Description
•