Crash in [@ mozilla::dom::ContentParent::RecvUpdateSHEntriesInBC ] "Trying to update a child BrowsingContext in another child process"
Categories
(Core :: DOM: Navigation, defect, P2)
Tracking
()
| Fission Milestone | M6 |
| Tracking | Status | |
|---|---|---|
| firefox75 | --- | unaffected |
| firefox76 | --- | wontfix |
People
(Reporter: cpeterson, Assigned: annyG)
References
(Regression)
Details
(Keywords: regression)
Crash Data
This crash is a diagnostic assertion failure added in bug 1546759.
Calixte says: "The moz_crash_reason is MOZ_DIAGNOSTIC_ASSERT(false) (Trying to update a child BrowsingContext in another child process)."
Anny says: "I think we are hitting this assertion because the BC we are trying to update is discarded thus is no longer owned by this process. Currently working on a patch."
P2 because the crash volume is low.
Does this crash affect non-Fission users?
|
Assignee | |
Comment 1•4 years ago
|
||
This crash can only happen if the sessionHistoryInParent and Fission prefs are both on at the same time which is an unsupported configuration.
https://searchfox.org/mozilla-central/rev/202a285024f174c2d2bf2152d9cba90a03723eab/docshell/base/nsDocShell.cpp#11384-11388
When the session history pref is off, the call toContentParent::RecvUpdateSHEntriesInBC does not take place.
I am closing this and I will mention this in our Fission sync meeting, which I haven't done till now because main folks working on session history know about the unsupported configuration.
|
||
Updated•4 years ago
|
|
||
Updated•4 years ago
|
Description
•