The next MemShrink meeting will be brought to you by the memory monitor dev
tool:
https://bugzilla.mozilla.org/show_bug.cgi?id=923275
The wiki page for this meeting is at:
https://wiki.mozilla.org/Performance/MemShrink
Agenda:
* Prioritize unprioritized MemShrink bugs.
* Discuss how we measur
Hi,
A few people noticed that we do not have a nice, searchable knowledge
base for Gecko tech. We have places to ask questions such as various
newsgroups, irc and places to document things like the wikis. It is hard
to search through all of that, so questions get repeated.
Lets give ask.mozil
On 2/3/14 12:36 PM, Gregory Szorc wrote:
Also, I believe chrome JS is never JIT compiled, so not getting JIT
benefits with generators doesn't seem like a concern?
Chrome JS running in a window context (
On 2/3/14, 9:13 AM, Boris Zbarsky wrote:
On 2/3/14 11:48 AM, Gregory Szorc wrote:
> what's the impact of this on performance?
It's hard to say without an example of the sort of code whose
performance we're worried about.
> because promises involve multiple function calls instead of a single
On 2/3/14 12:10 PM, Anne van Kesteren wrote:
Promise.jsm cannot be pure JS because JS doesn't have an event loop of itself.
Promise.jsm basically uses a JS-implemented nsIRunnable to the event
loop that then makes it process its entire pending list of callbacks.
So you only have one call from
On 2/3/14 11:48 AM, Gregory Szorc wrote:
> what's the impact of this on performance?
It's hard to say without an example of the sort of code whose
performance we're worried about.
> because promises involve multiple function calls instead of a single
> function call.
Note that in general not
On Mon, Feb 3, 2014 at 4:48 PM, Gregory Szorc wrote:
> If we switch Promise.jsm to DOM Promises, AFAICT we're moving from promises
> being 100% JS to involving a bridge to C++/DOM. Doesn't this add overhead
> and thus regress performance? Will it impact JIT behavior/perf anywhere?
Promise.jsm can
Firefox for android only uploads information when a webpage does a location
request, MozStumbler on the other hand allows you to permanents scan for
data to send so it will send a lot more information
On Sun, Feb 2, 2014 at 10:33 PM, Cameron McCormack wrote:
> Doug Turner wrote:
>
>> In the mea
On 1/31/14, 3:25 PM, Paolo Amadini wrote:
I have just filed bugs to make sure our DOM Promise implementation is
on par with Promise.jsm in these areas:
- Make state, value and reason inspectable in the debugger (bug 966471)
- Report all unhandled rejections to the Console on GC (bug 966452)
On 03.02.2014, at 15:55 , Wesley Hardman wrote:
> I get a 404 response when using either address. Is this the expected
> response? (My area is not mapped so I don't expect it to correctly find my
> location.)
Yes. You can read more about the API at:
http://mozilla-ichnaea.readthedocs.org/en/l
On 01/02/2014 22:11, Benjamin Smedberg wrote:
> Not sure if there's a better group to ask about WebAudio stuff
> specifically. Is there a way to keep WebAudio from "popping" when I
> start/stop an oscillator or change gain? The WebAudio spec claims that
> changes in gain should be dezippered to avo
On 2014-02-03 09:06, Hanno Schlichting wrote:
On 03.02.2014, at 02:03 , Doug Turner wrote:
One of the interesting things is that we can use this data to provide location based
services to Firefox. I switched my install of Firefox to use Mozilla Location Service
(MLS). You can try this by si
On 03.02.2014, at 07:09 , Philip Chee wrote:
> On 03/02/2014 09:03, Doug Turner wrote:
>> One of the interesting things is that we can use this data to provide
>> location based services to Firefox. I switched my install of Firefox
>> to use Mozilla Location Service (MLS). You can try this by si
On 03.02.2014, at 02:03 , Doug Turner wrote:
> One of the interesting things is that we can use this data to provide
> location based services to Firefox. I switched my install of Firefox to use
> Mozilla Location Service (MLS). You can try this by simply change the
> preference "geo.wifi.uri
14 matches
Mail list logo
