Closed
Bug 1709113
Opened 3 years ago
Closed 3 years ago
DefaultTabUnloaderMethods.iterateProcesses failed due to an unexpected object
Categories
(Firefox :: Tabbed Browser, defect)
Firefox
Tabbed Browser
Tracking
()
RESOLVED
FIXED
90 Branch
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox88 | --- | wontfix |
firefox89 | --- | wontfix |
firefox90 | --- | fixed |
People
(Reporter: toshi, Assigned: toshi)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
While testing TabUnloader, I saw DefaultTabUnloaderMethods.iterateProcesses failed because tab.linkedBrowser was null or a browser context's currentWindowGlobal was null.
Assignee | ||
Comment 1•3 years ago
|
||
Pushed by tkikuchi@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5a607f51940f Add null check in DefaultTabUnloaderMethods.iterateProcesses. r=NeilDeakin
Comment 3•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox90:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
Updated•3 years ago
|
Keywords: regression
Comment 4•3 years ago
|
||
Set release status flags based on info from the regressing bug 1682442
status-firefox88:
--- → affected
status-firefox89:
--- → affected
status-firefox-esr78:
--- → unaffected
Assignee | ||
Comment 5•3 years ago
|
||
TabUnloader
is disabled by default. To hit this bug, a user needs to enable this feature through the pref and to have a low-memory situation with more than 10 inactive tabs. Even if they hit the issue, a symptom is that tabs are not unloaded. Setting the status to wontfix.
Updated•3 years ago
|
Has Regression Range: --- → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•