1573939 - Assertion failure: sheet->ParsingMode() == aParsingMode, at /NREF-COMM-CENTRAL/mozilla/layout/style/Loader.cpp:989

Status: RESOLVED DUPLICATE of bug 1573639

(Core :: CSS Parsing and Computation, defect)

Description

[ISHIKAWA, Chiaki]

Attachment: Partial log of |make mozmill| test that contains a few instances of the same assertion failures.

My local environment.
Debian GNU/Linux AMD64

Since updating M-C and C-C a few hours ago, I have seen the following
bug during the testing of full DEBUG version of TB (comm-central) on
my local PC running linux.

Assertion failure: sheet->ParsingMode() == aParsingMode, at /NREF-COMM-CENTRAL/mozilla/layout/style/Loader.cpp:989

Based on the stack trace, I think, it could appear in Firefox as well.

The following is an excerpt from a log of |make mozmill| local test run.

  ... omission ...

TEST-PASS | /NREF-COMM-CENTRAL/mozilla/comm/mail/test/mozmill/attachment/test-attachment-events.js | test-attachment-events.js::test_no_attachment_renamed_on_blank
TEST-START | /NREF-COMM-CENTRAL/mozilla/comm/mail/test/mozmill/attachment/test-attachment-events.js | teardownModule
TEST-PASS | /NREF-COMM-CENTRAL/mozilla/comm/mail/test/mozmill/attachment/test-attachment-events.js | test-attachment-events.js::teardownModule
TEST-START | /NREF-COMM-CENTRAL/mozilla/comm/mail/test/mozmill/attachment/test-attachment-in-plain-msg.js | setupModule
TEST-PASS | /NREF-COMM-CENTRAL/mozilla/comm/mail/test/mozmill/attachment/test-attachment-in-plain-msg.js | test-attachment-in-plain-msg.js::setupModule
TEST-START | /NREF-COMM-CENTRAL/mozilla/comm/mail/test/mozmill/attachment/test-attachment-in-plain-msg.js | test_attachment_not_empty
++DOCSHELL 0x55ae3fb9d970 == 32 [pid = 26545] [id = {c183b881-aadd-48b8-a99e-3ca5a5f6f066}]
++DOMWINDOW == 95 (0x55ae3e4eda10) [pid = 26545] [serial = 106] [outer = (nil)]
++DOMWINDOW == 96 (0x55ae3e96f5b0) [pid = 26545] [serial = 107] [outer = 0x55ae3e4eda10]
++DOCSHELL 0x55ae39ea8640 == 33 [pid = 26545] [id = {128a6808-1b4c-4670-80d5-9ba081b0f2fc}]
++DOMWINDOW == 97 (0x55ae40124780) [pid = 26545] [serial = 108] [outer = (nil)]
++DOCSHELL 0x55ae40c26490 == 34 [pid = 26545] [id = {a45fb163-8733-45e5-829f-477b23bbc6f0}]
++DOMWINDOW == 98 (0x55ae3fac2040) [pid = 26545] [serial = 109] [outer = (nil)]
[26545, Main Thread] WARNING: NS_ENSURE_TRUE(root) failed: file /NREF-COMM-CENTRAL/mozilla/layout/base/nsDocumentViewer.cpp, line 3165
++DOMWINDOW == 99 (0x55ae39154aa0) [pid = 26545] [serial = 110] [outer = 0x55ae40124780]
++DOMWINDOW == 100 (0x55ae3fdd6fc0) [pid = 26545] [serial = 111] [outer = 0x55ae40124780]
++DOMWINDOW == 101 (0x55ae3f2aca00) [pid = 26545] [serial = 112] [outer = 0x55ae3fac2040]
NS_NewBufferedOutputStream: outputStream (= std::move(aOutputputStream)) =0x7fd748080468
--DOCSHELL 0x55ae40afbdd0 == 33 [pid = 26545] [id = {0f1bac8b-8594-418f-b9c1-54c803296c35}] [url = about:blank]
[26545, Main Thread] WARNING: '!ClientIsValidPrincipalInfo(mClientInfo.PrincipalInfo())', file /NREF-COMM-CENTRAL/mozilla/dom/clients/manager/ClientSource.cpp, line 176
[26545, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80550006: file /NREF-COMM-CENTRAL/mozilla/comm/mailnews/base/util/nsMsgDBFolder.cpp, line 4766
[26545, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80550006: file /NREF-COMM-CENTRAL/mozilla/comm/mailnews/local/src/nsMailboxService.cpp, line 616
++DOMWINDOW == 102 (0x55ae3e36c4e0) [pid = 26545] [serial = 113] [outer = 0x55ae40124780]
[26545, Main Thread] WARNING: Failed to retarget HTML data delivery to the parser thread.: file /NREF-COMM-CENTRAL/mozilla/parser/html/nsHtml5StreamParser.cpp, line 1142
[26545, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80550006: file /NREF-COMM-CENTRAL/mozilla/comm/mailnews/base/util/nsMsgDBFolder.cpp, line 4766
[26545, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80550006: file /NREF-COMM-CENTRAL/mozilla/comm/mailnews/local/src/nsMailboxService.cpp, line 616
Assertion failure: sheet->ParsingMode() == aParsingMode, at /NREF-COMM-CENTRAL/mozilla/layout/style/Loader.cpp:989
#01: mozilla::css::Loader::CreateSheet(nsIURI*, nsIContent*, nsIPrincipal*, mozilla::css::SheetParsingMode, mozilla::CORSMode, nsIReferrerInfo*, nsTSubstring<char16_t> const&, bool, mozilla::css::StyleSheetState&, RefPtr<mozilla::StyleSheet>) (/KERNEL-SRC/moz-obj-dir/objdir-tb3/dist/include/mozilla/Assertions.h:38 (discriminator 1))
#02: mozilla::css::Loader::LoadChildSheet(mozilla::StyleSheet, mozilla::css::SheetLoadData*, nsIURI*, mozilla::dom::MediaList*, mozilla::css::LoaderReusableStyleSheets*) (/NREF-COMM-CENTRAL/mozilla/layout/style/Loader.cpp:2160)
#03: LoadImportSheet(mozilla::css::Loader*, mozilla::StyleSheet*, mozilla::css::SheetLoadData*, mozilla::css::LoaderReusableStyleSheets*, mozilla::StyleCssUrl const&, already_AddRefed<RawServoMediaList>) (/NREF-COMM-CENTRAL/mozilla/layout/style/GeckoBindings.cpp:1750)
#04: Gecko_LoadStyleSheet (/KERNEL-SRC/moz-obj-dir/objdir-tb3/dist/include/mozilla/AlreadyAddRefed.h:145)
#05: core::ptr::<impl mut T>::is_null (/rustc/a53f9df32fbb0b5f4382caaad8f1a46f36ea887c/src/libcore/ptr.rs:1591)
#06: <style::stylesheets::rule_parser::TopLevelRuleParser as cssparser::rules_and_declarations::AtRuleParser>::rule_without_block (/NREF-COMM-CENTRAL/mozilla/servo/components/style/stylesheets/rule_parser.rs:267)
#07: <cssparser::rules_and_declarations::RuleListParser<P> as core::iter::traits::iterator::Iterator>::next (crtstuff.c:?)
#08: style::stylesheets::stylesheet::Stylesheet::parse_rules (/NREF-COMM-CENTRAL/mozilla/servo/components/style/stylesheets/stylesheet.rs:418)
#09: style::stylesheets::stylesheet::StylesheetContents::from_str (/NREF-COMM-CENTRAL/mozilla/servo/components/style/stylesheets/stylesheet.rs:86)
#10: Servo_StyleSheet_FromUTF8Bytes (/NREF-COMM-CENTRAL/mozilla/servo/ports/geckolib/glue.rs:1391)
#11: mozilla::StyleSheet::ParseSheet(mozilla::css::Loader, nsTSubstring<char> const&, mozilla::css::SheetLoadData*) (/KERNEL-SRC/moz-obj-dir/objdir-tb3/dist/include/mozilla/AlreadyAddRefed.h:128)
#12: mozilla::css::Loader::ParseSheet(nsTSubstring<char> const&, mozilla::css::SheetLoadData*, mozilla::css::Loader::AllowAsyncParse) (/KERNEL-SRC/moz-obj-dir/objdir-tb3/dist/include/mozilla/RefPtr.h:306)
#13: mozilla::css::StreamLoader::OnStopRequest(nsIRequest*, nsresult) (/NREF-COMM-CENTRAL/mozilla/layout/style/StreamLoader.cpp:111)
#14: nsBaseChannel::OnStopRequest(nsIRequest*, nsresult) (/NREF-COMM-CENTRAL/mozilla/netwerk/base/nsBaseChannel.h:241)
#15: nsInputStreamPump::OnStateStop() (/KERNEL-SRC/moz-obj-dir/objdir-tb3/dist/include/mozilla/RecursiveMutex.h:106)
#16: nsInputStreamPump::OnInputStreamReady(nsIAsyncInputStream*) (/NREF-COMM-CENTRAL/mozilla/netwerk/base/nsInputStreamPump.cpp:403)
#17: nsInputStreamReadyEvent::Run() (/NREF-COMM-CENTRAL/mozilla/xpcom/io/nsStreamUtils.cpp:175)
#18: nsThread::ProcessNextEvent(bool, bool*) (/NREF-COMM-CENTRAL/mozilla/xpcom/threads/nsThread.cpp:1229)
#19: NS_InvokeByIndex (/NREF-COMM-CENTRAL/mozilla/xpcom/reflect/xptcall/md/unix/xptcinvoke_asm_x86_64_unix.S:110)
#20: XPCWrappedNative::CallMethod(XPCCallContext&, XPCWrappedNative::CallMode) (/NREF-COMM-CENTRAL/mozilla/js/xpconnect/src/XPCWrappedNative.cpp:1195)
#21: XPC_WN_CallMethod(JSContext*, unsigned int, JS::Value*) (/NREF-COMM-CENTRAL/mozilla/js/xpconnect/src/XPCWrappedNativeJSOps.cpp:943)
#22: ??? (???:???)
Timeout: bridge.execFunction("9bb778c4-bebb-11e9-9661-0800272eef43", bridge.registry["{1d8241a0-1d9d-4b58-8176-6c88afca143d}"]["runTestDirectory"], ["/NREF-COMM-CENTRAL/mozilla/comm/mail/test/mozmill/attachment"])

TEST-UNEXPECTED-FAIL | Disconnect Error: Application unexpectedly closed
Timeout: bridge.set("f2a9d4b0-bebb-11e9-9661-0800272eef43", ChromeUtils.import('chrome://mozmill/content/modules/mozmill.jsm'))

     ... omission ...

Due to the assertion, the running TB terminates and the test run is aborted.

I realize there are more instances of the same assertion failure, and so I am uploading the partial log (I decided to abort the whole test because each assertion failure resulted in a long timeout).

Comment 1

[ISHIKAWA, Chiaki]

I did not see the assertion failure in the log the week before, so the regression window is the last couple of weeks (?).
It IS possible that the caller in the JavaScript side might have changed the value of the said parameter, but I have no idea at this moment.

Comment 2

[Emilio Cobos Álvarez (:emilio)]

See bug 1573639, there's a patch awaiting review that will fix it.