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
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
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
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
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
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
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
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
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
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
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,
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
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
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
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,
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?
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
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
- 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
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
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
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
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
___
23 matches
Mail list logo
