Re: Support for non-UTF-8 platform charset

On 11/25/2013 01:46 PM, Henri Sivonen wrote: > Questions: > > * On Windows, do we really need to pay homage to the pre-NT legacy > when doing Save As? How about we just use UTF-8 for "HTML Page, > complete" reserialization like on Mac? Do you mean Save As Text? Do we really use the platform char

Re: Is there any reason not to shut down bonsai?

On 11/21/13, 11:43 AM, Laura Thomson wrote: > If you don't know what that is--and few people do, which is even more > reason to shut it off--it's a search engine for some of our CVS > repositories, of which I think none are in active development. Thanks for the reminder that it still exists - I ju

Re: A/B testing with telemetry

Henri Sivonen wrote: Do we have a formalized way to do A/B testing with telemetry? That is, assuming that there is a telemetry probe that measures problem symptoms and a boolean pref for turning on a potential solution, is there a way the declare the pref as something that telemetry queries ca

Re: Reacting more strongly to low-memory situations in Firefox 25

- Original Message - > From: "Benjamin Smedberg" > To: dev-platform@lists.mozilla.org, "Bas Schouten" , > "David Major" , > "Nathan Froyd" , "Firefox Dev" > Sent: Monday, November 25, 2013 5:02:50 PM > Subject: Reacting more strongly to low-memory situations in Firefox 25 > > > Unf

Re: PSA: Shutting down my mozilla git mirror in three weeks

It looks like GitHub decided to disable Ehsan's repo and all forks without notice. https://bugzilla.mozilla.org/show_bug.cgi?id=943132 tracks it from our end. On 11/25/13, 11:39 PM, Ehsan Akhgari wrote: Dear all, For the past two and a half years I have been maintaining a git mirror of mozill

Re: Analyze C++/compiler usage and code stats easily

The repo was hiding that old changeset because it has been obsoleted (Mercurial changeset evolution magic). I updated the server config to expose hidden changesets, so the link works again. However, the changeset has been obsoleted, so you'll want to fetch the newest one. The best way to fet

Re: W3C Proposed Recommendations: Performance Timeline, User Timing, JSON-LD

On 11/25/13 7:07 PM, L. David Baron wrote: http://www.w3.org/TR/performance-timeline/ Performance Timeline http://www.w3.org/TR/user-timing/ User Timing Have we had anyone at all review these specs? My past experience with that working group and set of editors doesn't make me san

Re: Intent to replace Promise.jsm and promise.js with DOM Promises

On Mon, Nov 25, 2013 at 3:51 PM, wrote: > Based on bholley's comments on bug 939636, chrome code will need to do > > Cu.importGlobalProperties(["Promise"]); > > to use DOM Promises. > Well, more specifically, chrome code running in non-Window scopes (so JS-implemented Components, JSMs, privilege

Re: W3C Proposed Recommendations: XQuery, XPath, XSLT, EXI, API for Media Resources

On Tuesday 2013-10-29 12:01 +0200, Henri Sivonen wrote: > On Tue, Oct 29, 2013 at 1:39 AM, Ralph Giles wrote: > > On 2013-10-28 2:11 PM, L. David Baron wrote: > >> API for Media Resources 1.0 > >> http://www.w3.org/TR/mediaont-api-1.0/ > ... > > Thus I think we can be positive about this recom

Re: Proposed W3C Charters: Data Activity, {Data, CSV} on the Web

On Tuesday 2013-10-29 12:22 +0200, Henri Sivonen wrote: > On Mon, Oct 28, 2013 at 11:28 PM, L. David Baron wrote: > > W3C is proposing a data activity (an area of work) > ... > > Please reply to this thread if you think > > there's something we should say. > > Maybe it would make sense to abstain

W3C Proposed Recommendations: Performance Timeline, User Timing, JSON-LD

W3C recently published the following proposed recommendations (the stage before W3C's final stage, Recommendation): http://www.w3.org/TR/performance-timeline/ Performance Timeline http://www.w3.org/TR/user-timing/ User Timing http://www.w3.org/TR/json-ld/ JSON-LD 1.0: A JSON-based Se

Re: Intent to replace Promise.jsm and promise.js with DOM Promises

On Tuesday, November 19, 2013 10:48:24 AM UTC-8, Brandon Benvie wrote:> > There's two mostly orthogonal concerns here. The first is the sync/async > > issue: > > > > console.log(1); > > promise.resolve().then(() => { > >console.log(2); > > }); > > console.log(3

Re: Intent to replace Promise.jsm and promise.js with DOM Promises

On Monday, November 25, 2013 12:25:00 PM UTC-8, jsan...@gmail.com wrote: > Is there a consensus on removing Promise.jsm completely? As Benvie said, the > majority of work will be migrating over from `sdk/core/promise.js` (sync) to > the async Promise.jsm, which share APIs. Converting Promise.jsm

Re: [b2g] PSA: Shutting down my mozilla git mirror in three weeks

On Mon, Nov 25, 2013 at 1:46 PM, Aki Sasaki wrote: > Github has closed access to https://github.com/mozilla/mozilla-central : > > This repository has been disabled. > Access to this repository has been disabled by GitHub staff. > Contact support to restore access to this repository. >

Re: Reacting more strongly to low-memory situations in Firefox 25

On Mon, Nov 25, 2013 at 12:02:50PM -0500, Benjamin Smedberg wrote: > Note that in many cases, the user hasn't actually run out of memory: > they have plenty of physical memory and page file available. In most > cases they also have enough available VM space! Often, however, this > VM space is fragm

Re: Platform-specific nsICollation implementations

On 11/25/2013, 6:42 AM, Axel Hecht wrote: On 11/25/13 12:16 PM, Henri Sivonen wrote: Now that we have ICU in the tree, do we still need platform-specific nsICollation implementations? In particular, the Windows and Unix back ends look legacy enough that it seems that making nsICollation ICU-back

Re: Reacting more strongly to low-memory situations in Firefox 25

It seems that the 12MB reservation was aborting due to an invalid parameter. I've filed bug 943051. - Original Message - From: "Benjamin Smedberg" To: "Ehsan Akhgari" , dev-platform@lists.mozilla.org Sent: Monday, November 25, 2013 9:18:02 AM Subject: Re: Reacting more strongly to low-me

Re: Support for non-UTF-8 platform charset

Henri Sivonen writes: > On *nix platforms, it's not clear to me what exactly the platform > charset is used for these days. An MXR search turns up surprisingly > little. > * Do we (or gtk) really still support non-UTF-8 platform charset > values on *nix? (MXR turns up so little that it makes me

Re: Proposed changes to RelEng's OSX build and test infrastructure

On 11/22/2013, 3:44 PM, Johnathan Nightingale wrote: > On Nov 22, 2013, at 12:29 PM, Ted Mielczarek wrote: > >> On 11/21/2013 4:56 PM, John O'Duinn wrote: >>> 6) If a developer lands a patch that works on 10.9, but it fails somehow >>> on 10.7 or 10.8, it is unlikely that we would back out the fix

Re: Proposed changes to RelEng's OSX build and test infrastructure

On 11/22/2013, 12:29 PM, Ted Mielczarek wrote: > > I think this plan is generally sound. Users are moving en-masse to 10.9 > with the free update, so we should focus our resources there, and keep > 10.6 around to support those users that can't update for hardware > reasons. I just have one point o

Re: Intent to replace Promise.jsm and promise.js with DOM Promises

Is there a consensus on removing Promise.jsm completely? As Benvie said, the majority of work will be migrating over from `sdk/core/promise.js` (sync) to the async Promise.jsm, which share APIs. Converting Promise.jsm to consume DOM Promises is pretty straight forward, and would still give us ou

Re: Reacting more strongly to low-memory situations in Firefox 25

On 11/25/13 1:31 PM, Ryan VanderMeulen wrote: What does the OOM rate of 32bit builds on Win64 have to do with whether or not making 64bit Firefox builds would help? I think Benjamin's point was that only about 1/4 of the OOM crashes were on Win64 [1]. The rest were on Win32, and hence would n

Re: Reacting more strongly to low-memory situations in Firefox 25

On 11/25/2013 1:26 PM, Benjamin Smedberg wrote: This is an analysis of the crash reports from a particular day, so it's almost all going to be 32-bit Firefox because that's the only thing we release. 64-bit Firefox Nightly crashes due to OOM would be lumped into the OOM-win64 bucket in the analys

Re: Reacting more strongly to low-memory situations in Firefox 25

On 11/25/2013 1:09 PM, Ryan VanderMeulen wrote: So we're clear, this analysis is of 32bit Firefox builds running a 64bit Windows OS, right? So the process is still limited to 4GB of address space. Wouldn't a native 64bit Firefox build have significantly higher address space available to it? T

Re: Reacting more strongly to low-memory situations in Firefox 25

On 11/25/2013 12:02 PM, Benjamin Smedberg wrote:> Because one of the long-term possibilities discussed for solving this > issue is releasing a 64-bit version of Firefox, I additionally broke > down the "OOM" crashes into users running a 32-bit version of Windows > and users running a 64-bit versi

Re: Reacting more strongly to low-memory situations in Firefox 25

On 11/25/2013 12:02 PM, Benjamin Smedberg wrote: Because one of the long-term possibilities discussed for solving this issue is releasing a 64-bit version of Firefox, I additionally broke down the "OOM" crashes into users running a 32-bit version of Windows and users running a 64-bit version of W

Re: Reacting more strongly to low-memory situations in Firefox 25

On 11/25/2013 12:11 PM, Ehsan Akhgari wrote: Do we know how much memory we tend to use during the minidump collection phase? No, we don't. It seems that the Windows code maps all of the DLLs into memory again in order to extract information from them. Does it make sense to try to reserve an

Re: Reacting more strongly to low-memory situations in Firefox 25

On 2013-11-25 12:02 PM, Benjamin Smedberg wrote: Unfortunately, often when we are out of memory crash reports come back as empty minidumps (because the crash reporter has to allocation memory and/or VM space to create minidumps). We believe that most of the empty-minidump crashes present on crash

Reacting more strongly to low-memory situations in Firefox 25

In crashkill we have been tracking crashes that occur in low-memory situations for a while. However, we are seeing a troubling uptick of issues in Firefox 23 and then 25. I believe that some people may not be able to use Firefox because of these bugs, and I think that we should be reacting more

Re: A/B testing with telemetry

- Original Message - > Do we have a formalized way to do A/B testing with telemetry? That is, > assuming that there is a telemetry probe that measures problem > symptoms and a boolean pref for turning on a potential solution, is > there a way the declare the pref as something that telemetr

Re: Support for non-UTF-8 platform charset

Hi, > * Is the OS/2 port still alive and supported as an in-tree port? The > latest releases I've seen are 10.x ESR. the OS/2 port is alive, we already have a beta release for 17.x and a more current version will follow. -- Bye, Yuri Dario /* * OS/2 open source software * http://

PSA: Shutting down my mozilla git mirror in three weeks

Dear all, For the past two and a half years I have been maintaining a git mirror of mozilla-central plus a lot of the other branches that people found useful at https://github.com/mozilla/mozilla-central. Over the years this proved to be too much work for me to keep up with, and given the existen

Re: Unified builds

On 2013-11-23 7:22 AM, ISHIKAWA,chiaki wrote: (2013/11/23 1:41), Ehsan Akhgari wrote: On 2013-11-21 1:12 PM, ISHIKAWA,chiaki wrote: (2013/11/22 2:17), Ehsan Akhgari wrote: FWIW if this proves to be common, it's a huge problem since it would affect our crash stats etc... :( Well, if the prob

Re: Analyze C++/compiler usage and code stats easily

This patch doesn't seem to exist any more. Do you have another copy of it lying somewhere? Thanks! -- Ehsan On Fri, Nov 15, 2013 at 12:43 AM, Gregory Szorc wrote: > C++ developers, > > Over 90% of the CPU time required to build the tree is spent compiling or > link

Re: Is for...of on a live DOM node list supposed to do the right thing?

On Fri, Nov 22, 2013 at 6:00 PM, Boris Zbarsky wrote: > for (var x of Array.from(list)) > > to explicitly snapshot? Cross-browser compat might not be great so far, but > it's not for for..of either. Right. And going forward we'll make sure to introduce less live lists on the platform side. E.g

Re: Running a backout branch with Mercurial at JAWS.

On 25/11/13, 10:25 , Philip Chee wrote: Original blog post at An other problem with identifying a patch as Australis specific are patches with bits in Australis/browser and bits in Gecko (e.g. layout or content).

Re: Support for non-UTF-8 platform charset

On Tue, Nov 26, 2013 at 12:46 AM, Henri Sivonen wrote: > We have a concept of platform charset that goes back to pre-NT > Windows, Mac OS Classic, OS/2 and pre-UTF-8 *nix platforms. This > concept gets in the way of doCOMtaminating old code to use only new > facilities in mozilla::dom::EncodingUti

Re: Platform-specific nsICollation implementations

On 25/11/13 11:16, Henri Sivonen wrote: Now that we have ICU in the tree, do we still need platform-specific nsICollation implementations? In particular, the Windows and Unix back ends look legacy enough that it seems that making nsICollation ICU-backed would be a win. In particular, this woul

Support for non-UTF-8 platform charset

We have a concept of platform charset that goes back to pre-NT Windows, Mac OS Classic, OS/2 and pre-UTF-8 *nix platforms. This concept gets in the way of doCOMtaminating old code to use only new facilities in mozilla::dom::EncodingUtils. These days, on Mac and Android, we say the platform charset

Re: Platform-specific nsICollation implementations

On 11/25/13 12:16 PM, Henri Sivonen wrote: Now that we have ICU in the tree, do we still need platform-specific nsICollation implementations? In particular, the Windows and Unix back ends look legacy enough that it seems that making nsICollation ICU-backed would be a win. We don't build ICU ye

Platform-specific nsICollation implementations

Now that we have ICU in the tree, do we still need platform-specific nsICollation implementations? In particular, the Windows and Unix back ends look legacy enough that it seems that making nsICollation ICU-backed would be a win. -- Henri Sivonen hsivo...@hsivonen.fi http://hsivonen.fi/ _

Re: nsIPluginTagInfo::getDocumentEncoding()

On Sun, Nov 24, 2013 at 2:09 PM, Henri Sivonen wrote: > What's this API for? Looks like it's for this: http://www-archive.mozilla.org/projects/blackwood/java-plugins/api/org/mozilla/pluglet/mozilla/PlugletTagInfo2.html -- Henri Sivonen hsivo...@hsivonen.fi http://hsivonen.fi/ __

Running a backout branch with Mercurial at JAWS.

Original blog post at An other problem with identifying a patch as Australis specific are patches with bits in Australis/browser and bits in Gecko (e.g. layout or content). The bits in Gecko are necessary for Austra