Re: e10s is now enabled by default for Nightly!
Where can we read about how this decision was made? On my profiles with Force RTL, e10s perma-crashes ( https://bugzilla.mozilla.org/show_bug.cgi?id=1072980 ), and in most other cases, I only ever see spinners for remote content (ie can't actually browse the web - doesn't matter too much for me because I normally use beta). I recognize that my experience is not universal, but I hope it makes sense that I'm... surprised... that we're turning this on for everyone. ~ Gijs On 07/11/2014 00:27, Chris Peterson wrote: The patch is on mozilla-inbound and ought to hit mozilla-central in time for tomorrow's Nightly build. \o/ https://hg.mozilla.org/integration/mozilla-inbound/rev/a75897e664dd e10s will not ride the trains to Aurora 36. Talos and unit tests will continue to run for e10s and non-e10s until e10s hits the Release channel. Some known problems: * IME and a11y will disable e10s until support is completed * Some performance problems with Adblock Plus * Bug 947030 - Ghostery add-on does not block trackers * Bug 972507 - BugzillaJS add-on does not work [1] * Bug 1008768 - LastPass add-on does not fill in form fields * Bug 1014986 - HTTPS Everywhere add-on breaks HTTP redirects * Bug 1042680 - Tree Style Tabs add-on does not work * Bug 1042195 - 1Password add-on does not work * Bug 1058542 - NoScript add-on does not work * Bug 1093161 - Searching from address bar does not work the first time If you have any questions, drop by #e10s on IRC. If you file new bugs related to e10s, please include the word e10s in the summary so the e10s team's triage queries will find your bug. chris [1] btw, BugzillaJS is seeking a new maintainer: https://www.yammer.com/mozillians/#/threads/show?threadId=454089406 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
On 07/11/2014 10:40, Gijs Kruitbosch wrote: Where can we read about how this decision was made? On my profiles with Force RTL, e10s perma-crashes ( https://bugzilla.mozilla.org/show_bug.cgi?id=1072980 ), and in most other cases, I only ever see spinners for remote content (ie can't actually browse the web - doesn't matter too much for me because I normally use beta). I recognize that my experience is not universal, but I hope it makes sense that I'm... surprised... that we're turning this on for everyone. FWIW, my experience is pretty similar to yours. I'm forcing myself to use it for everyday work, but I completely dropped forceRTL and Flash (I must admit I'm not missing it) to make it usable. Sometimes it is hanging for seconds (white content in every tab) and the content process is crashing often. But in the end, it's usable. Nightly is for testing bleeding edge features and make them ready for prime time. We just got too much acquainted to a stable Nightly and that was not its scope, it was called Minefield for a reason. I'm happy we are enabling e10s for nightly testers if that allows it to improve faster, regardless of its status. -m ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
On 07/11/2014 10:12, Marco Bonardo wrote: On 07/11/2014 10:40, Gijs Kruitbosch wrote: Where can we read about how this decision was made? On my profiles with Force RTL, e10s perma-crashes ( https://bugzilla.mozilla.org/show_bug.cgi?id=1072980 ), and in most other cases, I only ever see spinners for remote content (ie can't actually browse the web - doesn't matter too much for me because I normally use beta). I recognize that my experience is not universal, but I hope it makes sense that I'm... surprised... that we're turning this on for everyone. FWIW, my experience is pretty similar to yours. I'm forcing myself to use it for everyday work, but I completely dropped forceRTL and Flash (I must admit I'm not missing it) to make it usable. Sometimes it is hanging for seconds (white content in every tab) and the content process is crashing often. But in the end, it's usable. Right, it's that last part that is very much not the case for me. I looked for a bug for a while and decided to just file one: https://bugzilla.mozilla.org/show_bug.cgi?id=1095407 Nightly is for testing bleeding edge features and make them ready for prime time. We just got too much acquainted to a stable Nightly and that was not its scope, it was called Minefield for a reason. I'm happy we are enabling e10s for nightly testers if that allows it to improve faster, regardless of its status. Maybe, but if we break people's browsers too badly for too long, I expect they'll just go back to more stable channels and/or $OTHERBROWSER, which defeats the point. There's a tradeoff here, and I'm interested as to what data/reasoning we used to decide what we did. ~ Gijs ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: About the bitfield requirement for portibility
On 21/10/2014 11:21, Xidorn Quan wrote: Hi, I read the C++ portibility guide [1], in which it is said that all bitfields should have the same type, or some compiler may mishandle the code. Is that still true for the compiler set we currently use? The compiler the doc mentioned is MSVC++8 which I believe we have dropped. Can we use different type for bitfields in a class in our new code? How about a link to http://blog.aaronballman.com/2011/08/the-joys-of-bit-fields/ ? Phil -- Philip Chee phi...@aleytys.pc.my, philip.c...@gmail.com http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
On Fri, Nov 7, 2014 at 11:38 AM, Gijs Kruitbosch gijskruitbo...@gmail.com wrote: Right, it's that last part that is very much not the case for me. I looked for a bug for a while and decided to just file one: https://bugzilla.mozilla.org/show_bug.cgi?id=1095407 My experience upgrading to today's nightly was also pretty bad. For me, it crashed on startup, every time, until I finally figured out a way to restart in safe mode. I've filed a bug with notes on what was happening: https://bugzilla.mozilla.org/show_bug.cgi?id=1095455 Also, I think the underlining of tab titles should have been fixed before enabling by default. I very much agree with Gijs that, in any case, my usage of Nightly is dependent on it being pretty usable almost every day, otherwise I have to retreat into something friendlier. Cheers, Dirkjan ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Introducing Brotli - an alternative to LZMA
Try this http://lists.w3.org/Archives/Public/public-webfonts-wg/2013Oct/att-0008/Brotli_update_-_20131011.pdf ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
Unfortunately, I checked it a patch yesterday (bug 1092156) that is causing lots of crashes if you have certain add-ons installed (such as the Gecko profiler). The crash happens regardless of whether e10s is enabled. Starting up in safe mode (via -safe-mode) fixes the problem. The bad patch has been backed out from m-c and we're building a new nightly. It's probably a good idea to wait to update for a few hours if you haven't already. Sorry about this, Bill - Original Message - From: Dirkjan Ochtman dirk...@ochtman.nl To: Gijs Kruitbosch gijskruitbo...@gmail.com Cc: dev-platform dev-platform@lists.mozilla.org Sent: Friday, November 7, 2014 5:37:53 AM Subject: Re: e10s is now enabled by default for Nightly! On Fri, Nov 7, 2014 at 11:38 AM, Gijs Kruitbosch gijskruitbo...@gmail.com wrote: Right, it's that last part that is very much not the case for me. I looked for a bug for a while and decided to just file one: https://bugzilla.mozilla.org/show_bug.cgi?id=1095407 My experience upgrading to today's nightly was also pretty bad. For me, it crashed on startup, every time, until I finally figured out a way to restart in safe mode. I've filed a bug with notes on what was happening: https://bugzilla.mozilla.org/show_bug.cgi?id=1095455 Also, I think the underlining of tab titles should have been fixed before enabling by default. I very much agree with Gijs that, in any case, my usage of Nightly is dependent on it being pretty usable almost every day, otherwise I have to retreat into something friendlier. Cheers, Dirkjan ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
On Fri, Nov 7, 2014 at 1:40 AM, Gijs Kruitbosch gijskruitbo...@gmail.com wrote: Where can we read about how this decision was made? On my profiles with Force RTL, e10s perma-crashes ( https://bugzilla.mozilla.org/ show_bug.cgi?id=1072980 ), and in most other cases, I only ever see spinners for remote content (ie can't actually browse the web - doesn't matter too much for me because I normally use beta). I recognize that my experience is not universal, but I hope it makes sense that I'm... surprised... that we're turning this on for everyone. As you might expect the decision was made based on us believing that we had had enough testing to have a good idea that the remaining bugs weren't bad enough to severely affect usage but wanted the additional testing that turning on in Nightly would give us. While most of the e10s team have been running with e10s enabled for a while at a certain point (as for any feature) we have to increase the number of testers to learn about bugs that we don't see in our configurations and usage patterns. We started that with prompting users to opt-in to e10s around a month ago and since then around 25% of Nightly users have been running with e10s enabled. As we hoped this saw a surge in the number of bugs filed and helped us understand the remaining issues more. Many many bugs have been fixed since then and as of Tuesday nothing remaining looked bad enough to block us turning this on more globally. The crash sounds like a late breaking change that should be fixed imminently, that's just the peril of nightly. Not being able to browse the web at all is an entirely new one that we hadn't seen in our testing to date. While it is unfortunate that this has broken the browser for you (and undoubtedly others) this is exactly the outcome we want for enabling a feature on nightly. More testing to reveal the bugs that the developers don't see themselves. Hopefully we'll get the most serious ones fixed quickly. If we can't then we get to talk about whether turning e10s off again is the right solution. I'm interested to know if you had opted in to e10s at all in the past and seen this issue with the permanent spinner? That might help us narrow down when it started to be a problem. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
Marco Bonardo schrieb: I'm forcing myself to use it for everyday work, but I completely dropped forceRTL and Flash (I must admit I'm not missing it) to make it usable. The Flash/Plugins stuff *should* have been fixed, but probably needs testing. KaiRo ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
On 07/11/2014 16:26, Dave Townsend wrote: wrote: Where can we read about how this decision was made? On my profiles with Force RTL, e10s perma-crashes ( https://bugzilla.mozilla.org/ show_bug.cgi?id=1072980 ), and in most other cases, I only ever see spinners for remote content (ie can't actually browse the web - doesn't matter too much for me because I normally use beta). I recognize that my experience is not universal, but I hope it makes sense that I'm... surprised... that we're turning this on for everyone. As you might expect the decision was made based on us believing that we had had enough testing to have a good idea that the remaining bugs weren't bad enough to severely affect usage but wanted the additional testing that turning on in Nightly would give us. While most of the e10s team have been running with e10s enabled for a while at a certain point (as for any feature) we have to increase the number of testers to learn about bugs that we don't see in our configurations and usage patterns. We started that with prompting users to opt-in to e10s around a month ago and since then around 25% of Nightly users have been running with e10s enabled. As we hoped this saw a surge in the number of bugs filed and helped us understand the remaining issues more. Many many bugs have been fixed since then and as of Tuesday nothing remaining looked bad enough to block us turning this on more globally. The crash sounds like a late breaking change that should be fixed imminently, that's just the peril of nightly. https://bugzilla.mozilla.org/show_bug.cgi?id=1072980 was filed 6 weeks ago, and diagnosed as relating to force rtl (but Firefox's fault, because we're passing CPOWs to functions that should never have them) within a few days, after which nothing happened. Not being able to browse the web at all is an entirely new one that we hadn't seen in our testing to date. While it is unfortunate that this has broken the browser for you (and undoubtedly others) this is exactly the outcome we want for enabling a feature on nightly. More testing to reveal the bugs that the developers don't see themselves. Hopefully we'll get the most serious ones fixed quickly. If we can't then we get to talk about whether turning e10s off again is the right solution. I'm interested to know if you had opted in to e10s at all in the past and seen this issue with the permanent spinner? That might help us narrow down when it started to be a problem. I duped the bug I filed to an earlier bug, courtesy of mak for finding those: https://bugzilla.mozilla.org/show_bug.cgi?id=1026521 That was filed 4.5 months ago. Both of these were marked blocking-e10s+ (although the top one got reset to ? just now - it's not clear to me why that happened). ~ Gijs ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
I had to file https://bugzilla.mozilla.org/show_bug.cgi?id=1095496 :( Mike. On 07 Nov 2014, at 17:33, Gijs Kruitbosch gijskruitbo...@gmail.com wrote: On 07/11/2014 16:26, Dave Townsend wrote: wrote: Where can we read about how this decision was made? On my profiles with Force RTL, e10s perma-crashes ( https://bugzilla.mozilla.org/ show_bug.cgi?id=1072980 ), and in most other cases, I only ever see spinners for remote content (ie can't actually browse the web - doesn't matter too much for me because I normally use beta). I recognize that my experience is not universal, but I hope it makes sense that I'm... surprised... that we're turning this on for everyone. As you might expect the decision was made based on us believing that we had had enough testing to have a good idea that the remaining bugs weren't bad enough to severely affect usage but wanted the additional testing that turning on in Nightly would give us. While most of the e10s team have been running with e10s enabled for a while at a certain point (as for any feature) we have to increase the number of testers to learn about bugs that we don't see in our configurations and usage patterns. We started that with prompting users to opt-in to e10s around a month ago and since then around 25% of Nightly users have been running with e10s enabled. As we hoped this saw a surge in the number of bugs filed and helped us understand the remaining issues more. Many many bugs have been fixed since then and as of Tuesday nothing remaining looked bad enough to block us turning this on more globally. The crash sounds like a late breaking change that should be fixed imminently, that's just the peril of nightly. https://bugzilla.mozilla.org/show_bug.cgi?id=1072980 was filed 6 weeks ago, and diagnosed as relating to force rtl (but Firefox's fault, because we're passing CPOWs to functions that should never have them) within a few days, after which nothing happened. Not being able to browse the web at all is an entirely new one that we hadn't seen in our testing to date. While it is unfortunate that this has broken the browser for you (and undoubtedly others) this is exactly the outcome we want for enabling a feature on nightly. More testing to reveal the bugs that the developers don't see themselves. Hopefully we'll get the most serious ones fixed quickly. If we can't then we get to talk about whether turning e10s off again is the right solution. I'm interested to know if you had opted in to e10s at all in the past and seen this issue with the permanent spinner? That might help us narrow down when it started to be a problem. I duped the bug I filed to an earlier bug, courtesy of mak for finding those: https://bugzilla.mozilla.org/show_bug.cgi?id=1026521 That was filed 4.5 months ago. Both of these were marked blocking-e10s+ (although the top one got reset to ? just now - it's not clear to me why that happened). ~ Gijs ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
https://bugzilla.mozilla.org/show_bug.cgi?id=1072980 was filed 6 weeks ago, and diagnosed as relating to force rtl (but Firefox's fault, because we're passing CPOWs to functions that should never have them) within a few days, after which nothing happened. ForceRTL is not a commonly installed add-on, which has reduced this bug's priority. I duped the bug I filed to an earlier bug, courtesy of mak for finding those: https://bugzilla.mozilla.org/show_bug.cgi?id=1026521 That was filed 4.5 months ago. This was believed to be mitigated (by disabling e10s when hardware acceleration was disabled), but thanks to your testing we discovered a bug in that mitigation: https://bugzilla.mozilla.org/show_bug.cgi?id=1095559 This is exactly the kind of testing we are hoping to get. We are making Nightly rougher to use (particularly this week as we shake out the major issues), but as Dave mentioned, we are doing this because it will help us ship e10s. Gavin On Fri, Nov 7, 2014 at 8:33 AM, Gijs Kruitbosch gijskruitbo...@gmail.com wrote: On 07/11/2014 16:26, Dave Townsend wrote: wrote: Where can we read about how this decision was made? On my profiles with Force RTL, e10s perma-crashes ( https://bugzilla.mozilla.org/ show_bug.cgi?id=1072980 ), and in most other cases, I only ever see spinners for remote content (ie can't actually browse the web - doesn't matter too much for me because I normally use beta). I recognize that my experience is not universal, but I hope it makes sense that I'm... surprised... that we're turning this on for everyone. As you might expect the decision was made based on us believing that we had had enough testing to have a good idea that the remaining bugs weren't bad enough to severely affect usage but wanted the additional testing that turning on in Nightly would give us. While most of the e10s team have been running with e10s enabled for a while at a certain point (as for any feature) we have to increase the number of testers to learn about bugs that we don't see in our configurations and usage patterns. We started that with prompting users to opt-in to e10s around a month ago and since then around 25% of Nightly users have been running with e10s enabled. As we hoped this saw a surge in the number of bugs filed and helped us understand the remaining issues more. Many many bugs have been fixed since then and as of Tuesday nothing remaining looked bad enough to block us turning this on more globally. The crash sounds like a late breaking change that should be fixed imminently, that's just the peril of nightly. https://bugzilla.mozilla.org/show_bug.cgi?id=1072980 was filed 6 weeks ago, and diagnosed as relating to force rtl (but Firefox's fault, because we're passing CPOWs to functions that should never have them) within a few days, after which nothing happened. Not being able to browse the web at all is an entirely new one that we hadn't seen in our testing to date. While it is unfortunate that this has broken the browser for you (and undoubtedly others) this is exactly the outcome we want for enabling a feature on nightly. More testing to reveal the bugs that the developers don't see themselves. Hopefully we'll get the most serious ones fixed quickly. If we can't then we get to talk about whether turning e10s off again is the right solution. I'm interested to know if you had opted in to e10s at all in the past and seen this issue with the permanent spinner? That might help us narrow down when it started to be a problem. I duped the bug I filed to an earlier bug, courtesy of mak for finding those: https://bugzilla.mozilla.org/show_bug.cgi?id=1026521 That was filed 4.5 months ago. Both of these were marked blocking-e10s+ (although the top one got reset to ? just now - it's not clear to me why that happened). ~ Gijs ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
My nightly crashes on start. Well, that's fine and is expected from unstable software. But now that I've submitted a half a dozen crash reports which pref do I flip to continue using my browser? ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
On 11/7/14 7:47 AM, Bill McCloskey wrote: Unfortunately, I checked it a patch yesterday (bug 1092156) that is causing lots of crashes if you have certain add-ons installed (such as the Gecko profiler). The crash happens regardless of whether e10s is enabled. Starting up in safe mode (via -safe-mode) fixes the problem. Maybe we should add a test configuration that runs our automated tests with some important add-ons installed? We're testing mozilla-inbound with a clean profile, unlike our human users. Testing with Gecko Profiler and some AMO Top 10 add-ons (like Adblock Plus) could catch regressions like this one. I have an Add-on Hell profile with AMO's top 30 add-ons installed that I occasionally load in a debug build of Firefox. :) chris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
If we have enabled e10s for nightly, are the normal non-e10s-test jobs going to run with the pref off? If not, we would be testing e10s twice on fx36, stop testing non-e10s fx36 and get non-e10s-regressions sneak into aurora when we uplift (since I believe we're locking to trunk). regards, Armen On 14-11-06 07:27 PM, Chris Peterson wrote: The patch is on mozilla-inbound and ought to hit mozilla-central in time for tomorrow's Nightly build. \o/ https://hg.mozilla.org/integration/mozilla-inbound/rev/a75897e664dd e10s will not ride the trains to Aurora 36. Talos and unit tests will continue to run for e10s and non-e10s until e10s hits the Release channel. Some known problems: * IME and a11y will disable e10s until support is completed * Some performance problems with Adblock Plus * Bug 947030 - Ghostery add-on does not block trackers * Bug 972507 - BugzillaJS add-on does not work [1] * Bug 1008768 - LastPass add-on does not fill in form fields * Bug 1014986 - HTTPS Everywhere add-on breaks HTTP redirects * Bug 1042680 - Tree Style Tabs add-on does not work * Bug 1042195 - 1Password add-on does not work * Bug 1058542 - NoScript add-on does not work * Bug 1093161 - Searching from address bar does not work the first time If you have any questions, drop by #e10s on IRC. If you file new bugs related to e10s, please include the word e10s in the summary so the e10s team's triage queries will find your bug. chris [1] btw, BugzillaJS is seeking a new maintainer: https://www.yammer.com/mozillians/#/threads/show?threadId=454089406 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
If we have enabled e10s for nightly, are the normal non-e10s-test jobs going to run with the pref off? Yes. Gavin On Fri, Nov 7, 2014 at 9:24 AM, Armen Zambrano arme...@mozilla.com wrote: If we have enabled e10s for nightly, are the normal non-e10s-test jobs going to run with the pref off? If not, we would be testing e10s twice on fx36, stop testing non-e10s fx36 and get non-e10s-regressions sneak into aurora when we uplift (since I believe we're locking to trunk). regards, Armen On 14-11-06 07:27 PM, Chris Peterson wrote: The patch is on mozilla-inbound and ought to hit mozilla-central in time for tomorrow's Nightly build. \o/ https://hg.mozilla.org/integration/mozilla-inbound/rev/a75897e664dd e10s will not ride the trains to Aurora 36. Talos and unit tests will continue to run for e10s and non-e10s until e10s hits the Release channel. Some known problems: * IME and a11y will disable e10s until support is completed * Some performance problems with Adblock Plus * Bug 947030 - Ghostery add-on does not block trackers * Bug 972507 - BugzillaJS add-on does not work [1] * Bug 1008768 - LastPass add-on does not fill in form fields * Bug 1014986 - HTTPS Everywhere add-on breaks HTTP redirects * Bug 1042680 - Tree Style Tabs add-on does not work * Bug 1042195 - 1Password add-on does not work * Bug 1058542 - NoScript add-on does not work * Bug 1093161 - Searching from address bar does not work the first time If you have any questions, drop by #e10s on IRC. If you file new bugs related to e10s, please include the word e10s in the summary so the e10s team's triage queries will find your bug. chris [1] btw, BugzillaJS is seeking a new maintainer: https://www.yammer.com/mozillians/#/threads/show?threadId=454089406 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
On 11/7/14 9:24 AM, Armen Zambrano wrote: If we have enabled e10s for nightly, are the normal non-e10s-test jobs going to run with the pref off? If not, we would be testing e10s twice on fx36, stop testing non-e10s fx36 and get non-e10s-regressions sneak into aurora when we uplift (since I believe we're locking to trunk). (A subset of) Talos and unit tests have been running with e10s already. We will continue to run tests for both e10s and non-e10s until e10s hits the Release channel. chris ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
On Fri, Nov 7, 2014 at 8:26 AM, Dave Townsend dtowns...@mozilla.com wrote: We started that with prompting users to opt-in to e10s around a month ago and since then around 25% of Nightly users have been running with e10s enabled. As we hoped this saw a surge in the number of bugs filed and helped us understand the remaining issues more. Many many bugs have been fixed since then and as of Tuesday nothing remaining looked bad enough to block us turning this on more globally. 25% is pretty high! Knowing that, the decision to turn it on by default does not seem unreasonable. Thinking ahead: e10s is a big enough change that I suspect we'll see high levels of instability when it gets uplifted to Aurora and (especially) Beta. Not sure how to avoid that... but will there be an easy way to disable it? I think there should be a pref in the user prefs (i.e. not just about:config) because it sounds like a non-trivial fraction of users will have add-ons broken by it. And does safe mode disable it? Nick ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
- Original Message - Thinking ahead: e10s is a big enough change that I suspect we'll see high levels of instability when it gets uplifted to Aurora and (especially) Beta. Not sure how to avoid that... but will there be an easy way to disable it? I think there should be a pref in the user prefs (i.e. not just about:config) because it sounds like a non-trivial fraction of users will have add-ons broken by it. And does safe mode disable it? There's already a check box in preferences that disables it. Nick ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
Yes, it is currently disabled by safe mode. There is currently a checkbox in prefs to toggle it, in Nightly builds. When it rides the trains, we'll have to re-evaluate that tradeoff at various steps based on the quality level and testing goals. In the long term it does not make sense to maintain that as a user-exposed option. Gavin On Fri, Nov 7, 2014 at 1:28 PM, Nicholas Nethercote n.netherc...@gmail.com wrote: On Fri, Nov 7, 2014 at 8:26 AM, Dave Townsend dtowns...@mozilla.com wrote: We started that with prompting users to opt-in to e10s around a month ago and since then around 25% of Nightly users have been running with e10s enabled. As we hoped this saw a surge in the number of bugs filed and helped us understand the remaining issues more. Many many bugs have been fixed since then and as of Tuesday nothing remaining looked bad enough to block us turning this on more globally. 25% is pretty high! Knowing that, the decision to turn it on by default does not seem unreasonable. Thinking ahead: e10s is a big enough change that I suspect we'll see high levels of instability when it gets uplifted to Aurora and (especially) Beta. Not sure how to avoid that... but will there be an easy way to disable it? I think there should be a pref in the user prefs (i.e. not just about:config) because it sounds like a non-trivial fraction of users will have add-ons broken by it. And does safe mode disable it? Nick ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
On 11/7/14 1:28 PM, Nicholas Nethercote wrote: On Fri, Nov 7, 2014 at 8:26 AM, Dave Townsenddtowns...@mozilla.com wrote: We started that with prompting users to opt-in to e10s around a month ago and since then around 25% of Nightly users have been running with e10s enabled. As we hoped this saw a surge in the number of bugs filed and helped us understand the remaining issues more. Many many bugs have been fixed since then and as of Tuesday nothing remaining looked bad enough to block us turning this on more globally. 25% is pretty high! Knowing that, the decision to turn it on by default does not seem unreasonable. You can see the e10s telemetry numbers at [1]. Technically, E10S_AUTOSTART is the number of browser sessions, not users, with e10s enabled. Perhaps there are only a few e10s testers and they're constantly crashing and restarting their browser session. :) We have a list of tested add-ons with their compatibility status and relevent bug numbers at http://arewee10syet.com/ chris [1] https://telemetry.mozilla.org/#filter=nightly%2F36%2FE10S_AUTOSTARTrenderhistogram=Graph ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
Are we currently planning to let this default ride into aurora in 2 weeks' time? ~ Gijs On 07/11/2014 21:44, Gavin Sharp wrote: Yes, it is currently disabled by safe mode. There is currently a checkbox in prefs to toggle it, in Nightly builds. When it rides the trains, we'll have to re-evaluate that tradeoff at various steps based on the quality level and testing goals. In the long term it does not make sense to maintain that as a user-exposed option. Gavin On Fri, Nov 7, 2014 at 1:28 PM, Nicholas Nethercote n.netherc...@gmail.com wrote: On Fri, Nov 7, 2014 at 8:26 AM, Dave Townsend dtowns...@mozilla.com wrote: We started that with prompting users to opt-in to e10s around a month ago and since then around 25% of Nightly users have been running with e10s enabled. As we hoped this saw a surge in the number of bugs filed and helped us understand the remaining issues more. Many many bugs have been fixed since then and as of Tuesday nothing remaining looked bad enough to block us turning this on more globally. 25% is pretty high! Knowing that, the decision to turn it on by default does not seem unreasonable. Thinking ahead: e10s is a big enough change that I suspect we'll see high levels of instability when it gets uplifted to Aurora and (especially) Beta. Not sure how to avoid that... but will there be an easy way to disable it? I think there should be a pref in the user prefs (i.e. not just about:config) because it sounds like a non-trivial fraction of users will have add-ons broken by it. And does safe mode disable it? Nick ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: e10s is now enabled by default for Nightly!
On Fri, Nov 7, 2014 at 4:39 PM, Gijs Kruitbosch gijskruitbo...@gmail.com wrote: Are we currently planning to let this default ride into aurora in 2 weeks' time? From Chris's first message: e10s will not ride the trains to Aurora 36. - Ryan ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
