Closed
Bug 1554785
Opened 5 years ago
Closed 5 years ago
Limit webIsolated process count per-site to 1
Categories
(Core :: DOM: Content Processes, defect, P2)
Core
DOM: Content Processes
Tracking
()
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
References
Details
Attachments
(2 files)
No description provided.
Assignee | ||
Comment 1•5 years ago
|
||
This allows the # of processes to be specified for remote types like
"webIsolated", used by fission windows.
Assignee | ||
Comment 2•5 years ago
|
||
This is the more logical behaviour than the previous, where an unknown process
would be given the full "dom.ipc.processCount" process limit, which could lead
to unintentionally allocating a large # of processes.
Pushed by nlayzell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f93fe7aa9c43 Part 1: Support dynamic remote types for GetMaxProcessCount, r=farre https://hg.mozilla.org/integration/autoland/rev/59b619fd9899 Part 2: Default to 1 process for unknown remote types, r=farre
Comment 4•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f93fe7aa9c43
https://hg.mozilla.org/mozilla-central/rev/59b619fd9899
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox69:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in
before you can comment on or make changes to this bug.
Description
•