Thanks Benoit! It is indeed a nice milestone. Congrats are due to nical, Bas,
and pretty much all of the graphics team for all the work on the layers
refactoring and OMTC.
On Wednesday, November 27, 2013 1:25:53 PM UTC+13, Benoit Jacob wrote:
> Congrats Nick, after all is said and done, this is
On Wed, Nov 27, 2013 at 9:36 AM, Gabriele Svelto wrote:
> What's the general feeling about this? The relevant MDN page [2] mentions
> that WONTFIX should only be used by module owners and peers so that also
> makes me wary of using it even though in some cases I'm pretty sure a bug
> won't ever be
On 27/11/13 07:36, Gabriele Svelto wrote:
> I'm always tempted to close the former as duplicates of the actual fix
> and the latter as WONTFIX so that they won't show up on the following
> searches but I'm also afraid that closing a bug several years old is
> akin to thread necromancy [1].
Validly
On 11/25/13 11:02 AM, Benjamin Smedberg wrote:
== Regression ranges ==
Some of the issues appear to be recently introduced in Firefox 25. We
need to jump on regression ranges ASAP. I could really use help working
with users such as those identified at the top of this message to see if
there are
Years from now the stories will go... "I had to walk to school through 10ft
deep snow, uphill both ways, and when I got there, we had to do OGL compositing
on the main thread".
Now, all reading this and running Nightly on Linux, and having
layers.acceleration.force-enabled set, please try to br
I’ve been aware of these proposals. Honestly, there’s not a lot of meat in the
performance timeline proposal and one of the editors doesn’t appear to be
actively involved anymore.
IMO, this is implementation detail for describing the data structures used by a
timeline “entry”. I’m not sure how
I'll take a closer look at it. Will be interesting to see how this fits in with
what we're planning, but so far, we didn't plan on taking it into account.
- Original Message -
From: "Rob Campbell"
To: "Till Schneidereit"
Cc: "Boris Zbarsky" , "Axel Kratel" ,
dev-platform@lists.mozilla.
On 11/27/13 11:51 AM, Rob Campbell wrote:
IMO, this is implementation detail for describing the data structures used by a
timeline “entry”
There are specs that expose these entries too, so this is not
implementation detail but something we'll need to end up implementing
when Facebook and com
I can't figure out what, if anything, this discussion implies about
the ballot on the Proposed Recommendations. At this point I'm
inclined not to respond to the vote.
-David
--
𝄞 L. David Baron http://dbaron.org/ 𝄂
𝄢 Mozilla https://www.moz
- Original Message -
> On 27/11/13 07:36, Gabriele Svelto wrote:
> > I'm always tempted to close the former as duplicates of the actual fix
> > and the latter as WONTFIX so that they won't show up on the following
> > searches but I'm also afraid that closing a bug several years old is
> >
On 11/27/13 2:03 PM, L. David Baron wrote:
I can't figure out what, if anything, this discussion implies about
the ballot on the Proposed Recommendations.
I'm not sure.
Basically, I think we're in a sucky situation here:
1) These are specs that we'll need to implement.
2) We were not involv
Lawrence Mandel writes:
> - Original Message -
>> On 27/11/13 07:36, Gabriele Svelto wrote:
>> > I'm always tempted to close the former as duplicates of the
>> > actual fix and the latter as WONTFIX so that they won't show
>> > up on the following searches but I'm also afraid that closing
Benjamin Smedberg schrieb:
On 11/25/13 8:15 PM, Bas Schouten wrote:
I'm a little confused, when I force OOM my firefox build on 64-bit
windows it -definitely- goes down before it reaches more than 3GB of
working set. Am I missing something here?
I think so. I did not mention working set at all.
A 64-bit build would, but we "don't ship" those.
A win64 machine running a 32-bit program can have 4GB of VM, though.
-Jeff
- Original Message -
From: "Robert Kaiser"
To: dev-platform@lists.mozilla.org
Sent: Wednesday, November 27, 2013 4:35:36 PM
Subject: Re: Reacting more strongly to l
Jeff Gilbert schrieb:
A 64-bit build would, but we "don't ship" those.
A win64 machine running a 32-bit program can have 4GB of VM, though.
OK, just wanted to make sure. Benjamin looked at 25.0 release data,
AFAIK, so that's of course only 32bit, but if we look at Nightly data, I
think a sign
On 11/21/13, 10:38 PM, Gregory Szorc wrote:
On 11/20/13, 9:57 PM, Gregory Szorc wrote:
On 11/19/2013 10:08 PM, Gregory Szorc wrote:
On 11/18/13, 11:15 PM, Gregory Szorc wrote:
Do builds feel like they've gotten faster in the last few weeks^hours?
It's because they have.
When I did my MacBook
On 28/11/2013 06:06, Gregory Szorc wrote:
On de5aa094b55f, we're now down to:
Wall 7:37 (457)
User 45:38 (2738)
Sys3:54 (234)
Total 49:32 (2972)
That's with WebRTC and ICU enabled.
Looking at my own stats while building I was wondering if anybody has
looked at peak memory consum
On 11/28/13, 12:21 PM, Gabriele Svelto wrote:
On 28/11/2013 06:06, Gregory Szorc wrote:
On de5aa094b55f, we're now down to:
Wall 7:37 (457)
User 45:38 (2738)
Sys3:54 (234)
Total 49:32 (2972)
That's with WebRTC and ICU enabled.
Looking at my own stats while building I was wonderi
On 28/11/2013 08:09, Gregory Szorc wrote:
Peak RSS likely has increased significantly (hundreds to gigabytes
range).
OK, that's what I was curious about.
Memory is cheap and getting cheaper. Nobody paid by Mozilla to develop
Firefox should have a machine with less than 16 GB. Adding 25%+ to b
On 11/28/13, 2:29 PM, Gabriele Svelto wrote:
On 28/11/2013 08:09, Gregory Szorc wrote:
Peak RSS likely has increased significantly (hundreds to gigabytes
range).
OK, that's what I was curious about.
Memory is cheap and getting cheaper. Nobody paid by Mozilla to develop
Firefox should have a
20 matches
Mail list logo
