e10s-multi update and tests

Blake Kaplan mrbkap at mozilla.com
Wed Mar 22 23:45:59 UTC 2017

Hello all,

As some of you might have noticed, we are now defaulting to 4 content
processes on Nightly builds! We're continuing to collect data and
planning on running experiments with different numbers of processes to
generate more data and allow us to fine-tune our defaults and
strategies for process allocation.

As part of our effort to enable e10s-multi on Nightly, we disabled a
few tests that were misbehaving. We've re-enabled most of them and are
on track to finish re-enabling them (after verifying that the problem
was in the test and not the underlying code).

As we get to the end of that effort, I'd like to ask everybody to
think about any areas that they feel are not tested with multiple
content processes that should be. Obviously, as we find regressions
related to multiple content processes we'll add regression tests, but
I would like to avoid having any last-minute panics over missing


More information about the firefox-dev mailing list