1342195 - all new tabs opened in same process while second process only has one tab

Status: RESOLVED INVALID

(Core :: DOM: Content Processes, defect)

Description

[Ben Kelly [:bkelly, not reviewing]]

My current nightly session has some strange multi-e10s behavior.  Every tab I open ends up in one process.  The other content process has a single tab in it:

Process 1:

├──392.20 MB (51.69%) -- window-objects
│  ├──118.47 MB (15.61%) ++ top(https://mail.google.com/mail/u/2/#label/-BZ-Watch/15a6c8f1ca4f713e, id=4294967297)
│  ├──100.63 MB (13.26%) ++ top(https://mail.google.com/mail/u/0/#inbox, id=4294967301)
│  ├───69.93 MB (09.22%) ++ top(https://mail.google.com/mail/u/1/#inbox, id=4294967303)
│  ├───43.98 MB (05.80%) ++ top(https://twitter.com/, id=4294971426)
│  ├───31.87 MB (04.20%) ++ top(https://calendar.google.com/calendar/b/2/render?tab=mc#main_7, id=4294967299)
│  ├───18.44 MB (02.43%) ++ top(https://web.telegram.org/#/im?p=u112692817_4411017454867641282, id=4294967307)
│  └────8.87 MB (01.17%) ++ top(https://bugzilla.mozilla.org/page.cgi?id=mydashboard.html, id=4294967305)

Process 2:

├──122.87 MB (42.44%) ++ window-objects/top(https://irccloud.mozilla.com/#!/ircs://irc1.dmz.scl3.mozilla.com:6697/%23content, id=2147483652)

I've closed my twitter tab and re-opened it in a new tab three times now.  Each time it ends back up in the first process.

Is it possible that the "ignore bad memory process" patch that landed marked process 2 as bad?  If that is the case, shouldn't there be a new second process started up to replace it?

Comment 1

[Ben Kelly [:bkelly, not reviewing]]

I tried a few more times and finally got it to switch.  I guess this is probably just unpredictable behavior thanks to the rand() call in process selection.

Comment 2

[Benjamin Smedberg]

FWIW, in about:telemetry if we had marked one as bad you should be able to see a scalar dom.contentprocess.troubled_due_to_memory in the current session.