Crash in [@ mozilla::net::LoadInfo::Release]
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox106 | --- | unaffected |
firefox107 | --- | unaffected |
firefox108 | --- | fixed |
People
(Reporter: gsvelto, Unassigned)
References
(Regression)
Details
(Keywords: crash, regression, topcrash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/ddc49868-4bef-4af8-8180-5ff720221104
MOZ_CRASH Reason: MOZ_RELEASE_ASSERT(NS_IsMainThread()) (Wrong thread!)
Top 10 frames of crashing thread:
0 xul.dll mozilla::net::LoadInfo::Release netwerk/base/LoadInfo.cpp:848
1 xul.dll nsCOMPtr_base::~nsCOMPtr_base xpcom/base/nsCOMPtr.h:328
1 xul.dll NS_GetFinalChannelURI netwerk/base/nsNetUtil.cpp:2301
2 xul.dll nsContentUtils::ShouldResistFingerprinting dom/base/nsContentUtils.cpp:2242
3 xul.dll mozilla::dom::Document::PreferredColorScheme const dom/base/Document.cpp:17847
4 xul.dll Gecko_ComputeSystemColor layout/style/GeckoBindings.cpp:680
5 xul.dll style::gecko::media_queries::Device::system_nscolor servo/components/style/gecko/media_queries.rs:454
5 xul.dll style::values::specified::color::SystemColor::compute servo/components/style/values/specified/color.rs:356
5 xul.dll enum2$<style::values::specified::color::Color>::to_computed_color servo/components/style/values/specified/color.rs:664
6 xul.dll style::values::specified::color::impl$8::to_computed_value servo/components/style/values/specified/color.rs:675
It seems like we're manipulating a URI on the wrong thread. I'm not sure if this is a style computation problem or a fingerprinting-resistance one.
It only happens for me with privacy.resistFingerprinting = true
.
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=7a26d2290b51df8a28c18073dfcb077e0577e5d0&tochange=f90b376b2c985c66f19e77d6d703afd8d5e140c3
Regressed by Bug 1544127.
Comment 2•3 years ago
|
||
:jesup, since you are the author of the regressor, bug 1544127, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
Comment 4•3 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 desktop browser crashes on nightly
:emilio, could you consider increasing the severity of this top-crash bug?
For more information, please visit auto_nag documentation.
Comment 5•3 years ago
|
||
Bug 1799435 should fix this.
Updated•3 years ago
|
Description
•