Crash in [@ mozilla::css::StreamLoader::~StreamLoader]
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox73 | --- | unaffected |
firefox74 | --- | unaffected |
firefox75 | blocking | fixed |
People
(Reporter: philipp, Assigned: emilio)
References
(Regression)
Details
(Keywords: crash, regression, topcrash)
Crash Data
Attachments
(7 files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
1.09 MB,
image/png
|
Details | |
28.65 KB,
text/plain
|
Details | |
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-release-
|
Details | Review |
283.33 KB,
image/png
|
Details |
This bug is for crash report bp-88d4a8a3-fd6e-4e73-a8d4-4b8ec0200215.
Top 10 frames of crashing thread:
0 xul.dll mozilla::css::StreamLoader::~StreamLoader layout/style/StreamLoader.cpp:24
1 xul.dll mozilla::css::StreamLoader::~StreamLoader layout/style/StreamLoader.cpp:23
2 xul.dll mozilla::EditorEventListener::Release editor/libeditor/EditorEventListener.cpp:293
3 xul.dll mozilla::css::Loader::LoadSheet layout/style/Loader.cpp
4 xul.dll mozilla::css::Loader::LoadChildSheet layout/style/Loader.cpp:2236
5 xul.dll LoadImportSheet layout/style/GeckoBindings.cpp:1537
6 xul.dll Gecko_LoadStyleSheet layout/style/GeckoBindings.cpp:1577
7 xul.dll geckoservo::stylesheet_loader::{{impl}}::request_stylesheet servo/ports/geckolib/stylesheet_loader.rs:61
8 xul.dll cssparser::rules_and_declarations::parse_at_rule<style::stylesheets::rule_parser::TopLevelRuleParser, style_traits::StyleParseErrorKind> third_party/rust/cssparser/src/rules_and_declarations.rs:475
9 xul.dll static style::stylesheets::stylesheet::Stylesheet::parse_rules servo/components/style/stylesheets/stylesheet.rs:491
this crash is appearing in nightly build 20200215095617 with MOZ_DIAGNOSTIC_ASSERT(mOnStopRequestCalled || mAsyncOpenFailed)
.
Assignee | ||
Comment 1•4 years ago
|
||
Thanks for filing! I'll follow-up in the bug that added the assertion.
Assignee | ||
Comment 2•4 years ago
|
||
This is a bug in the diagnostic patch in bug 1605895, so I'll address here instead.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 3•4 years ago
|
||
This can happen with invalid @import rules in userContent / userChrome.css
Assignee | ||
Comment 4•4 years ago
|
||
I'm going to land this because:
- It's a pretty annoying / hard to diagnose startup crash.
- There's no changes for release builds, only for nightly.
Cam, could you sanity-check it? We don't really care about sync loads for the purposes of diagnosing bug 1605895.
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/361b2704db9f Fix diagnostics for error paths in sync loads.
Assignee | ||
Comment 6•4 years ago
|
||
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a41e6a90419d Fix a test after the previous patch.
Assignee | ||
Comment 8•4 years ago
|
||
Updated•4 years ago
|
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ba1a49bfe104 Add a missing file for the test for this bug... d'oh.
Comment 10•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/361b2704db9f
https://hg.mozilla.org/mozilla-central/rev/a41e6a90419d
https://hg.mozilla.org/mozilla-central/rev/ba1a49bfe104
Comment 11•4 years ago
|
||
There still are some crashes after the patch landed: https://mzl.la/2STz1rd
The moz_crash_reason is always: MOZ_DIAGNOSTIC_ASSERT(mOnStopRequestCalled || mChannelOpenFailed)
:emilio, could you have a look ?
Assignee | ||
Comment 12•4 years ago
|
||
Yeah, that's actually the bug we were looking for. Will nag the necko people in the other bug.
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 13•4 years ago
|
||
Pascal, is this a topcrash with the fix in this bug? it seems from the link in comment 11 there's only been 12 crashes since it landed.
Comment 14•4 years ago
|
||
This bug is said to be fixed for FF 75, but I am still getting it regularly: https://crash-stats.mozilla.org/report/index/4d55b6d5-8cb4-4227-aa81-ca3530200314
What is even worse, it not only generates a complete crash-hang of FF but it also consistently corrupts session, killing some pinned tabs -- see a few of placeholder globe favicons after the restart. This is quite annoying since I can not always remember what was there.
Can somebody please look at my crash report to see if it is really the same bug or a new one?
Thanks in advance.
Comment 15•4 years ago
|
||
There's many crashes now in 75beta.
Assignee | ||
Comment 16•4 years ago
|
||
That crash is different from the one fixed here, and is tracked in bug 1605895.
I'll nag the necko people there... But is there any chance you could attach your about:support
? May you have extensions that may modify stylesheets or something that could help reproduce this?
Assignee | ||
Updated•4 years ago
|
Comment 17•4 years ago
|
||
Comment 18•4 years ago
|
||
Unfortunately, there is no clear pattern of action to reproduce this but it happens mainly when I click on a video link in a YT notification mail in Thunderbird. The tab opens but it immediately crashes. But it does not happen every time.
Comment 19•4 years ago
|
||
Please specify a root cause for this bug. See :tmaity for more information.
Comment 20•4 years ago
|
||
Emilio, can you please check progress in #bug 1605895?
This bug is security-sensitivity so I can not see it but I wonder why it is not fixed yet for so long, especially since it is quite a nasty bug (that also yanks some of my tabs every time, which did not happen in FF for years already) with well over thousand of crashes in recent weeks, a serious regression over FF 74 which did not have such issues at all.
Thanks in advance.
Assignee | ||
Comment 21•4 years ago
|
||
So I thought that MOZ_DIAGNOSTIC_ASSERT
was disabled on dev-edition / etc. This assertion should be disabled on the release channel so it shouldn't cause crashes there... but apparently is unconditionally enabled in dev-edition which seems unfortunate.
There is progress from the networking folks in that bug as far as I can tell. But I'll remove this assertion for now as they served their purpose already.
Assignee | ||
Comment 22•4 years ago
|
||
btw, if you can reproduce this somewhat frequently by all means tell me how :)
Assignee | ||
Comment 23•4 years ago
|
||
We confirmed that this is a networking issue, no point in making beta /
devedition crash due to this. Still worth keeping it on nightly to monitor the
crash volume once the networking fix arrives.
Assignee | ||
Comment 24•4 years ago
|
||
Comment on attachment 9138110 [details]
Bug 1615832 - Make an assertion nightly-only.
Beta/Release Uplift Approval Request
- User impact if declined: unnecessary crashes for beta / devedition users.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Just downgrading a diagnostic assertion so that we don't crash. The lack of the assertion itself doesn't cause any security issues.
- String changes made/needed: none
Comment 25•4 years ago
|
||
Alas, I can not reproduce it via a step-by-step method but the crashes happen only when I open links in new tabs, never during any other action. Crashes kill one of the multiple firefox.exe processes along with a few tabs (pinned, at least in my case).
But the issue is it does not happen on every action of opening a link in a new tab, it only happens once in a few dozens of such actions resulting in crashes happening only once or twice a day despite very active use of the browser. This forbids me from recording the bug (capturing minidump) at least in a regular WinDbg mode which generates a giant file very quickly (maybe I could do it if I had Mac Pro with 1.5 TB of RAM though).
Comment 26•4 years ago
|
||
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7c9ac7d5bef4 Make an assertion nightly-only.
Comment 27•4 years ago
|
||
bugherder |
Comment 28•4 years ago
|
||
Comment on attachment 9138110 [details]
Bug 1615832 - Make an assertion nightly-only.
76 is on Beta now.
Comment 29•4 years ago
|
||
Comment on attachment 9138110 [details]
Bug 1615832 - Make an assertion nightly-only.
diagnostic asserts are off on release, I think we're fine here.
Assignee | ||
Updated•4 years ago
|
Comment 30•4 years ago
•
|
||
I can reproduce the crash with 100% certainty as follow.
On Android, in any application using an embedded browser such as slack or nine mail client.
Select "open in Firefox Nightly"
It will crash, guaranteed
Latest crash report: bp-429e9dd8-04d6-4ab2-b4f3-e8cf20200903
Comment 31•4 years ago
|
||
Updated•4 years ago
|
Description
•