Do we have a clear definition of "content process"? I.e. does/will it include:
- GMP processes (no?) - GPU process (probably not?) - file:// URL processes (probably should?) - Web Extensions processes (probably should?) - ServiceWorker processes (probably should?) Thanks. Nick On Thu, Mar 23, 2017 at 10:45 AM, Blake Kaplan <mrb...@mozilla.com> wrote: > 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 > tests. > > Thanks. > -- > Blake > _______________________________________________ > firefox-dev mailing list > firefox-...@mozilla.org > https://mail.mozilla.org/listinfo/firefox-dev > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
