Closed Bug 1212046 Opened 9 years ago Closed 2 years ago

[e10s] [dom.ipc.processCount > 1] unloaded tabs assigned a content process

Categories

(Core :: DOM: Content Processes, defect)

defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
e10s - ---

People

(Reporter: mesvam, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20151006004017

Steps to reproduce:

1. Enable session restore on startup
2. Set dom.ipc.processCount = 2 (or higher) in about:config
3. Leave open exactly one window with two tabs. (e.g. wikipedia.org and youtube.com)
4. Close window to stop FF. (Or File > Exit)
5. Start FF


Actual results:

Two content processes (plugin-container.exe) are spawned, though only one window is loaded/active.


Expected results:

Only one content process should be loaded at startup. The second process should spawn when the user focus on the other tab, causing it to load.

If dom.ipc.processCount is set to a high number, and many tabs are restored, memory usage dramatically increases on startup due to per-process overhead, even though only a few tabs are being used.
tracking-e10s: --- → -
Component: General → DOM: Content Processes
Product: Firefox → Core
Version: 43 Branch → Trunk
Seems to have been fixed by a recent update. Mark as fixed?
That "fixed" likely is a mere side-effect of bug 1227275. Any fix to that might restore the old behavior since the current tab to process distribution logic is simply round-robin.

This behavior has likely greatly changed with Fission.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.