1360535 - Not getting e10s with cohort=multiBucket2 (beta 54)

Status: RESOLVED WORKSFORME

(Core :: DOM: Content Processes, defect)

Description

[Andrew Overholt [:overholt]]

Is this expected?

Acer Aspire E15, Windows 10, fresh installation of beta

Comment 1

[Andrew Overholt [:overholt]]

Blake, this is the scenario I briefly mentioned to you. Anything I can do to diagnose? In about:support I just see "0/1 (Disabled)". No addons other than the system ones because this is a brand new clean profile on a brand new Windows 10 non-touchscreen laptop.

Comment 2

[Gabor Krizsanits (INACTIVE)]

Hey Andrew, Blake is on PTO today, so I've needinfo-ed Felipe, he might know the answer too, or have the right questions. Do you have any add-ons installed? I'm not sure if we disable e10s for some old style, non-bootstrapped add-ons on beta, but that could explain it.

Comment 3

[Jim Mathies [:jimm]]

Can we get a copy of the about:support text?

Comment 4

[:Felipe Gomes (needinfo for replies!)]

Hey, sorry for the huge list of prefs below, but instead of asking them bit by bit, here's a list of everything (I think) I need to debug this:

extensions.e10sMultiBlockedByAddons
extensions.e10sBlockedByAddons
e10s.rollout.cohort
e10s.rollout.cohortSample
e10s.rollout.cohortSample.multi
extensions.e10s.rollout.policy
extensions.e10s.rollout.hasAddon

Comment 5

[Andrew Overholt [:overholt]]

(In reply to Gabor Krizsanits [:krizsa :gabor] from comment #2)
> Hey Andrew, Blake is on PTO today

Oops, I knew that :) (but I also wasn't expecting a response today ;).

> Do you have any add-ons
> installed?

No. I'll attach about:support in a sec.

(In reply to :Felipe Gomes (needinfo me!) from comment #4)
> extensions.e10sMultiBlockedByAddons

false

> extensions.e10sBlockedByAddons

false

> e10s.rollout.cohort

multiBucket2

> e10s.rollout.cohortSample

0.561340

> e10s.rollout.cohortSample.multi

0.468207

> extensions.e10s.rollout.policy

50allmpc

> extensions.e10s.rollout.hasAddon

false

Comment 6

[Andrew Overholt [:overholt]]

Attachment: about:support

Comment 7

[:Felipe Gomes (needinfo for replies!)]

So from your about:support, the e10srollout addon ran correctly and set these two prefs:

browser.tabs.remote.autostart.2: true
dom.ipc.processCount.web: 2

You definitely should be getting e10s. Did you restart the browser with this profile at least once?

The only way that it would say "0/1 (Disabled)" is if it gets here: http://searchfox.org/mozilla-central/rev/068e6f292503df13515a52321fc3844e237bf6a9/toolkit/xre/nsAppRunner.cpp#5051

And it should not be getting there with the browser.tabs.remote.autostart.2=true pref that you have.

Comment 8

[Andrew Overholt [:overholt]]

After restarting it now says "0/1 (Disabled by accessibility tools)" in about:support.

Comment 9

[:Felipe Gomes (needinfo for replies!)]

So for the original report of e10s being disabled, according to those prefs values and some IRC talks, it probably was just the fact that the browser needed a restart so that the new values can take effect.