Re: nsThread now leaks runnables if dispatch fails

On Wed, Jan 6, 2016 at 3:53 AM, Kyle Huey wrote: > On Mon, Jan 4, 2016 at 4:10 PM, Randell Jesup wrote: >> >> Yup. In cases where we anticipate a possible Dispatch failure (which is >> supposed to become impossible, but isn't currently) you can use the >>

Re: C++ Core Guidelines

On Thu, Oct 1, 2015 at 9:58 PM, Jonathan Watt wrote: > For those who are interested in this, there's a bug to consider integrating > the Guidelines Support Library (GSL) into the tree: > > https://bugzilla.mozilla.org/show_bug.cgi?id=1208262 This bug appears to have stalled.

Proposed changes to Talos (performance) alerting

I'd like to propose some changes in how we report and triage Talos alerts. Over the past couple years, Joel Maher (with occasional assistance from myself and others) has taken over the job of triaging and responding to ("sheriffing") Talos regressions. He's done this through a bunch of

Re: nsThread now leaks runnables if dispatch fails

Xidorn Quan writes: > On Thu, Jan 7, 2016 at 6:47 AM, Karl Tomlinson wrote: >> Xidorn Quan writes: >> >>> You can keep a raw pointer yourself, and release it manually after you >>> find the dispatch fails, like what is done in >>> NS_DispatchToCurrentThread [1]. It is ugly,

Re: nsThread now leaks runnables if dispatch fails

On Thu, Jan 7, 2016 at 6:47 AM, Karl Tomlinson wrote: > Xidorn Quan writes: > >> On Wed, Jan 6, 2016 at 3:53 AM, Kyle Huey wrote: >>> On Mon, Jan 4, 2016 at 4:10 PM, Randell Jesup wrote: Yup. In cases where we anticipate a

W3C Proposed Recommendation: Web Storage (Second Edition)

A W3C Proposed Recommendation is available for the membership of W3C (including Mozilla) to vote on, before they proceed to the final stage of being W3C Recomendation: Web Storage (Second Edition) http://www.w3.org/TR/webstorage/ deadline: January 8, 2016 (Friday!) This specification is

Proposed W3C Charter: Web Authentication Working Group

The W3C is proposing a charter for: Web Authentication Working Group http://www.w3.org/2015/12/web-authentication-charter.html https://lists.w3.org/Archives/Public/public-new-work/2015Dec/0010.html Mozilla has the opportunity to send comments or objections through January 25. Please reply

Re: "-Moz-Element" -like API by extending WEBGL_dynamic_texture

On Wed, Jan 6, 2016 at 9:50 PM, Robert O'Callahan wrote: > Where would you put that flag? Simplest would be an HTTP header I suppose. > I think this has basically the same problems: very difficult to specify and > police, and fragile when the content changes. At least

Re: W3C Proposed Recommendation: Web Storage (Second Edition)

On Thu, Jan 7, 2016 at 6:05 AM, L. David Baron wrote: > This specification is derived from an upstream WHATWG specification. And therefore hasn't removed the storage mutex concept it seems. Not sure if that's careworthy since we don't implement from TR/ anyway, but I thought

Re: C++ Core Guidelines

Henri Sivonen wrote: > On Thu, Oct 1, 2015 at 9:58 PM, Jonathan Watt wrote: > > For those who are interested in this, there's a bug to consider > integrating > > the Guidelines Support Library (GSL) into the tree: > > > >

Re: nsThread now leaks runnables if dispatch fails

Xidorn Quan writes: > On Wed, Jan 6, 2016 at 3:53 AM, Kyle Huey wrote: >> On Mon, Jan 4, 2016 at 4:10 PM, Randell Jesup wrote: >>> >>> Yup. In cases where we anticipate a possible Dispatch failure (which is >>> supposed to become impossible, but isn't

windbg now available as a --debugger option to |mach run| etc.

|mach run| and |mach mochitest|, among other things, accept a --debugger argument, which defaults to using MSVC on Windows. Bug 1236983, currently on inbound, modifies things so you can say --debugger=windbg and things should Just Work. It should even work if windbg is not on your $PATH; if it

Re: "-Moz-Element" -like API by extending WEBGL_dynamic_texture

On Wed, Jan 6, 2016 at 9:52 PM, Anne van Kesteren wrote: > On Tue, Jan 5, 2016 at 10:18 PM, Robert O'Callahan > wrote: > > That's an option, but it's a very large problem that's very difficult to > > get right. And there are so many things that need to be