Open Bug 1863238 Opened 6 months ago Updated 6 months ago

Crash in [@ nsHtml5Parser::Parse]

Categories

(Core :: DOM: HTML Parser, defect)

Other
All
defect

Tracking

()

Tracking Status
firefox119 --- affected
firefox120 --- affected
firefox121 --- affected

People

(Reporter: release-mgmt-account-bot, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/e8212337-4288-4f92-a422-a38580231013

MOZ_CRASH Reason: MOZ_RELEASE_ASSERT(!(GetStreamParser() && !aKey)) (Got a null key in a non-script-created parser)

Top 10 frames of crashing thread:

0  xul.dll  nsHtml5Parser::Parse  parser/html/nsHtml5Parser.cpp:222
1  xul.dll  mozilla::dom::Document::WriteCommon  dom/base/Document.cpp:10026
2  xul.dll  mozilla::dom::Document::Write  dom/base/Document.cpp:10036
2  xul.dll  mozilla::dom::Document_Binding::write  dom/bindings/DocumentBinding.cpp:3717
3  xul.dll  mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ThrowExceptions>  dom/bindings/BindingUtils.cpp:3327
4  xul.dll  CallJSNative  js/src/vm/Interpreter.cpp:486
4  xul.dll  js::InternalCallOrConstruct  js/src/vm/Interpreter.cpp:580
4  xul.dll  InternalCall  js/src/vm/Interpreter.cpp:647
4  xul.dll  js::CallFromStack  js/src/vm/Interpreter.cpp:652
4  xul.dll  js::Interpret  js/src/vm/Interpreter.cpp:3407

By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:

  • First crash report: 2023-09-27
  • Process type: Content
  • Is startup crash: No
  • Has user comments: No
  • Is null crash: Yes - 1 out of 8 crashes happened on null or near null memory address
Component: General → DOM: HTML Parser

The only known bug that could potentially have this effect (though it's not supposed to) is bug 1849107. So either that or something unknown.

Looking at crashes with these signature in the last two weeks, they all had that crash reason.

While this would be nice to fix, the volume isn't super high.

Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.