1333798 - session restored tabs seem to cluster in one content process

Status: RESOLVED INVALID

(Core :: DOM: Content Processes, defect)

Description

[Ben Kelly [:bkelly, not reviewing]]

Since multi-e10s was enabled in nightly with 2 content processes I have noticed:

1) Of my nine tabs, the vast majority end up in one content process.  8-to-1 and 7-to-2 so far.
2) Most of the tabs in the larger content process were opened by session restore when I launched the browser.
3) Most of the tabs in the larger content process are pinned tabs that load immediately.

Does session restore start before we have spawned the second content process or something?

Comment 1

[Gabor Krizsanits (INACTIVE)]

Ben, I tried to reproduce this but couldn't. Is this something you can reproduce reliably? Maybe some of those tabs are special (I would check if we skip any process in ContentParent::RandomSelect because of the opener).

Comment 2

[Ben Kelly [:bkelly, not reviewing]]

Well, as bug 1342195 I find it hard to interpret the tab selection policy.  You can probably close this if you can't reproduce.  I really wish we could move to something predictable even if its not perfect.  Seems like people are bikeshedding bug 1333799.

Comment 3

[Gabor Krizsanits (INACTIVE)]

(In reply to Ben Kelly [not reviewing due to deadline][:bkelly] from comment #2)
> Well, as bug 1342195 I find it hard to interpret the tab selection policy. 
> You can probably close this if you can't reproduce.  I really wish we could
> move to something predictable even if its not perfect.  Seems like people
> are bikeshedding bug 1333799.

Yeah, the 'choose the process with the least tabs' approach mentioned there seems like a good start, I'll talk to Blake if he can work on it next week or I'll pick it up.