Closed
Bug 1664961
Opened 4 years ago
Closed 4 years ago
Crash in nsDocShell::Reload() in browser_security-1.js with SessionHistoryInParent
Categories
(Core :: DOM: Navigation, defect, P2)
Core
DOM: Navigation
Tracking
()
Tracking | Status | |
---|---|---|
firefox82 | --- | fixed |
People
(Reporter: jesup, Assigned: jesup)
References
Details
Attachments
(1 file)
If you enable SessionHistoryInParent for fission, bc11 crashes in browser_security-1.js in nsDocShell::Reload(), because ContentChild::GetSingleton() is null (since it's not running in the child).
It needs to check if we're in the parent, like most other uses of GetSingleton().
Updated•4 years ago
|
Component: DOM → Preferences
Product: Remote Protocol → Firefox
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
This is a fission session-history bug; moving to DOM:Navigation
Component: Preferences → DOM: Navigation
Product: Firefox → Core
Updated•4 years ago
|
Assignee | ||
Comment 3•4 years ago
|
||
Pushed by rjesup@wgate.com: https://hg.mozilla.org/integration/autoland/rev/1088f83fc64f check if child process when processing docshell Reload() r=smaug
Comment 5•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox82:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•