<div dir="ltr"><div><div>The patch has been backed out because of the merge. To be continued on next Monday.<br></div>More info about the back-out: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1303113#c9">https://bugzilla.mozilla.org/show_bug.cgi?id=1303113#c9</a><br><br></div>-Gabor<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 10, 2016 at 1:29 AM, Blake Kaplan <span dir="ltr"><<a href="mailto:mrbkap@mozilla.com" target="_blank">mrbkap@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello everyone,<br>
<br>
We've been working on the e10s-multi project for a while now and are<br>
looking at turning on multiple content processes in Nightly. Our plan<br>
is to start with two content processes (compared to the single content<br>
process we currently use) and if that goes well, we'll start ramping<br>
up the number of content processes we use as well as playing with more<br>
exciting process allocation strategies. We are not yet planning to<br>
ride the trains.<br>
<br>
In order to turn on in Nightly, Gabor Krizsanits has been doing a ton<br>
of work to make sure our tests are green. We've had to disable a<br>
couple of them in e10s mode and for others we've been forcing them to<br>
use a single content process (to be clear, the tests themselves are<br>
broken with multiple content processes and the underlying code is<br>
not). We will be working on fixing the tests as we can as well as<br>
turning the disabled tests back on [1].<br>
<br>
We have two known bugs that we're enabling with:<br>
* Service workers for the same origin can run simultaneously in<br>
multiple processes [2]. We expect the user-visible aspects of this bug<br>
to be limited to desktop notifications being duplicated (for each<br>
content process that has a bogus service worker running in it). bkelly<br>
is leading a team to fix this.<br>
<br>
* DOM storage doesn't properly propagate changes to other processes<br>
[3]. This could cause web sites to misbehave. janv is working on<br>
fixing this.<br>
<br>
Let Gabor or me know if you have any concerns or comments and needinfo<br>
us on bugs that you run into.<br>
<br>
[1] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1315042" rel="noreferrer" target="_blank">https://bugzilla.mozilla.org/<wbr>show_bug.cgi?id=1315042</a><br>
[2] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1231208" rel="noreferrer" target="_blank">https://bugzilla.mozilla.org/<wbr>show_bug.cgi?id=1231208</a><br>
[3] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=666724" rel="noreferrer" target="_blank">https://bugzilla.mozilla.org/<wbr>show_bug.cgi?id=666724</a><br>
<span class="HOEnZb"><font color="#888888">--<br>
Blake<br>
______________________________<wbr>_________________<br>
dev-platform mailing list<br>
<a href="mailto:dev-platform@lists.mozilla.org">dev-platform@lists.mozilla.org</a><br>
<a href="https://lists.mozilla.org/listinfo/dev-platform" rel="noreferrer" target="_blank">https://lists.mozilla.org/<wbr>listinfo/dev-platform</a><br>
</font></span></blockquote></div><br></div>