Crash in [@ mozilla::dom::Navigation::InnerFireNavigateEvent]
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox138 | --- | disabled |
firefox139 | --- | disabled |
firefox140 | --- | disabled |
firefox141 | --- | affected |
People
(Reporter: mccr8, Assigned: farre)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: crash, regression, topcrash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/bad94f01-7f8c-4d2e-b337-be26d0250515
MOZ_CRASH Reason:
MOZ_DIAGNOSTIC_ASSERT(!mOngoingNavigateEvent)
Top 10 frames:
0 xul.dll mozilla::dom::Navigation::InnerFireNavigateEvent(JSContext*, mozilla::dom::Na... dom/navigation/Navigation.cpp:764
1 xul.dll mozilla::dom::Navigation::FirePushReplaceReloadNavigateEvent(JSContext*, mozi... dom/navigation/Navigation.cpp:551
2 xul.dll nsDocShell::AddState(JS::Handle<JS::Value>, nsTSubstring<char16_t> const&, ns... docshell/base/nsDocShell.cpp:11409
3 xul.dll nsHistory::PushOrReplaceState(JSContext*, JS::Handle<JS::Value>, nsTSubstring... dom/base/nsHistory.cpp:271
4 xul.dll nsHistory::PushState(JSContext*, JS::Handle<JS::Value>, nsTSubstring<char16_t... dom/base/nsHistory.cpp:222
4 xul.dll mozilla::dom::History_Binding::pushState(JSContext*, JS::Handle<JSObject*>, v... dom/bindings/HistoryBinding.cpp:381
5 xul.dll mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::Nor... dom/bindings/BindingUtils.cpp:3302
6 xul.dll CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), js::... js/src/vm/Interpreter.cpp:494
6 xul.dll js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstru... js/src/vm/Interpreter.cpp:590
6 xul.dll InternalCall(JSContext*, js::AnyInvokeArgs const&, js::CallReason) js/src/vm/Interpreter.cpp:657
Comment 1•3 months ago
|
||
Set release status flags based on info from the regressing bug 1948254
:farre, since you are the author of the regressor, bug 1948254, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Reporter | ||
Comment 2•3 months ago
|
||
This is a diagnostic assert, so maybe the non-Nightly branches could be set to "disabled", if there's no real concern about the behavior there.
Updated•3 months ago
|
Assignee | ||
Comment 3•3 months ago
|
||
This is a known issue and a spec bug. It's also something only present with the "dom.navigation.webidl.enabled"
pref enabled.
Assignee | ||
Updated•3 months ago
|
Updated•3 months ago
|
Comment 4•3 months ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 AArch64 and ARM crashes on nightly
:farre, could you consider increasing the severity of this top-crash bug?
For more information, please visit BugBot documentation.
Assignee | ||
Comment 5•2 months ago
|
||
It's behind a pref, so shouldn't be a problem.
Assignee | ||
Updated•2 months ago
|
Description
•