Firefox 55.* in Windows/Ubuntu - every day CPU 100%/Hangs Up. Please to do something!

Dear developers of Firefox, I have 55.* version of Firefox at work and at home At work i have Windows 7 OS, at home the Ubuntu 16.04 LTE I have my own synced profile. I don't have problem with syncing... In both OSes i regulary and every day i see the situation when after few work time (may be

Re: Moving from xulrunner to firefox SDK

On Friday, 25 August 2017 20:58:06 UTC+5:30, Myk Melez wrote: > > Manish > > 2017 August 21 at 23:53 > > from where can I find the latest firefox SDK version for all the > > platforms eg: windows, linux and mac. Second can the directory > > structure remains

Re: Device Memory header and JS API

On 2017-09-06 11:48 AM, Tom Ritter wrote: Steam's hardware survey shows the following distribution percentages. Less than 512 MB 0.00% 512 Mb to 999 MB 0.03% 1 GB 0.52% 2 GB 3.30% 3 GB 6.27% 4 GB 14.96% 5 GB 0.66% 6 GB 3.23% 7 GB 2.33% 8 GB 42.77% 9 GB 0.04% 10 GB 0.29% 11 GB 0.18% 12

Re: Device Memory header and JS API

On Wed, Sep 6, 2017 at 2:53 PM, Daniel Veditz wrote: > I do not know what are plans are about Client Hints in general, whether we > intend to or when, and obviously that's a prerequisite. > Client Hints is https://bugzilla.mozilla.org/show_bug.cgi?id=935216, FWIW.

Coding style: Placement of binary operators when breaking a long line

Hi folks- *Note: Previously we've discussed the placement of logical operators && and ||; a decision was made and I do not wish to re-litigate that here*. Currently we have a somewhat convoluted set of rules about where to place boolean operators when breaking long lines [1]. Essentially we say

Intermittent oranges and when to disable the related test case - a simplified policy

Over the last 9 months a few of us have really watched intermittent test failures almost daily and done a lot to pester people as well as fix many. While there are over 420 bugs that have been fixed since the beginning of the year, there are half that many (211+) which have been disabled in

Re: Proposal: Unified Bootstrap Stages for Gecko

On Tuesday, September 5, 2017 at 8:18:40 AM UTC-7, Mike Conley wrote: > We should also consider adding a milestone for the "hero element" for > the browser. There's some discussion fragments in bug 1369417 about this > (which I see you're already involved in! Great!), captured from a very >

Re: Device Memory header and JS API

On Tue, Sep 5, 2017 at 10:13 AM, Shubhie Panicker via dev-platform < dev-platform@lists.mozilla.org> wrote: > Boris expressed privacy concern with the API and suggested starting a > thread here to get some concrete feedback. ​It's great that you agreed to send this (and other client hints?)

Re: Intermittent oranges and when to disable the related test case - a simplified policy

In order to be more consistent, marking a failing test as disabled should be done with a keyword instead of a whiteboard tag. Proposed keyword: test-disabled Description: Used by test automation team to indicate the failing test associated with this bug has a failure rate above a threshold level

Re: Telemetry Histogram Expiry

I don't think this probe is needed any more. Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1397371 to remove it. On Wed, Sep 6, 2017 at 1:55 AM, wrote: > The following histograms will be expiring on 2017-09-20, and should be > removed from the codebase, or

Re: Intent to implement: RTCRtpTransceiver

IIRC, the rework won't be able to be switched 'back-to-existing' with a pref, but we'll continue to respect existing disable-webrtc prefs and the --disable-webrtc compiler switch, right? -tom On Wed, Sep 6, 2017 at 11:41 AM, Byron Campen wrote: > What:

Re: Device Memory header and JS API

This is pretty concerning to me from a fingerprinting POV. The spec currently rounds up to one of the following values: 0.25, 0.5, 0.75, 1, 1.5, 2, 3, 4, 6, 8, 12, 16, 24, 32, 48, 64, 96, 128 Steam's hardware survey shows the following distribution percentages. Less than 512 MB 0.00% 512 Mb to

Kris Maglione and Andrew McCreight are now XPConnect Peers

XPConnect is not exactly a fun module. When I took the reins from mrbkap 4.5 years ago, Peter wiped a tear from his eye and said "Congratulations, Blake." Still, it's at the heart of Gecko, and needs ongoing attention from deep hackers. With the old hands busy with other things recently, Kris and

Re: Intermittent oranges and when to disable the related test case - a simplified policy

Andrew Swan noticed that whiteboard tag was showing up on bugs not filed by the intermittent-test-failure bot (thanks!) Here's the queries restricted to just bot filed bugs: https://mzl.la/2eMnMRz (add ons) https://mzl.la/2eMaPqQ (all core/ffx/toolkit) This begs the question, why was that

Re: Coding style: Placement of binary operators when breaking a long line

On Wed, Sep 06, 2017 at 12:30:58PM -0700, Eric Rahm wrote: > Hi folks- > > *Note: Previously we've discussed the placement of logical operators && and > ||; a decision was made and I do not wish to re-litigate that here*. > > Currently we have a somewhat convoluted set of rules about where to

Re: Intermittent oranges and when to disable the related test case - a simplified policy

On Wed, Sep 6, 2017 at 4:53 PM, Emma Humphries wrote: > This begs the question, why was that whiteboard tag being used that way? > ​Surely there are other reasons to disable tests, and people might want to track those too. If you want to restrict your new keyword to just

Re: Coding style: Placement of binary operators when breaking a long line

As I said, I was hoping to avoid rehashing this point, but the general consensus from the last rather contentious post [1] was that changing from the prevalent style of the codebase for primarily aesthetic reasons was hard to justify (points about readability were made on both sides). Nick pointed

Re: Kris Maglione and Andrew McCreight are now XPConnect Peers

On 9/6/17 7:47 PM, Bobby Holley wrote: Andrew became a peer in May, and Kris become a peer a few minutes ago. Excellent. Congrats to them both! And I do mean congrats, not condolences. ;) -Boris ___ dev-platform mailing list

Re: Device Memory header and JS API

Why do the numbers need to be standardized? Could we give browsers the ability to change the value in response to their understanding of the current situation. Surely an Android device is easily identifiable as such, so we could choose values that reflect our Android population at the current

Re: Intent to ship version 4 of the Safe Browsing protocol

On August 18, 2017 at 2:57:13 AM, Mike Hommey (m...@glandium.org) wrote: On Wed, Aug 16, 2017 at 12:43:19PM -0700, Daniel Veditz wrote: > 100 options is 4950 configurations to test. I think you mean 2^100. That's 1.26 x 10^30. Also known as “a boatload.” Eric Shepherd Senior Technical

Re: Intermittent oranges and when to disable the related test case - a simplified policy

Andy To start: https://bugzilla.mozilla.org/buglist.cgi?product=Core=Firefox=Firefox%20for%20Android=Firefox%20for%20iOS=Toolkit_format=advanced=---_whiteboard=test%20disabled%2Ctest-disabled%2Ctestdisabled_whiteboard_type=anywordssubstr=bug_id=0 Add-ons, Web Extensions, and Plugins related:

Re: Intermittent oranges and when to disable the related test case - a simplified policy

Is there an easy way for me to track what tests have been disabled as result of intermittent issues we haven't been able to fix? On 6 September 2017 at 14:10, wrote: > Over the last 9 months a few of us have really watched intermittent test > failures almost daily and done

Re: Intermittent oranges and when to disable the related test case - a simplified policy

Cool, thanks. On 6 September 2017 at 16:32, Emma Humphries wrote: > Andy > > To start: > >

Re: Coding style: Placement of binary operators when breaking a long line

On 09/06/2017 09:03 PM, Eric Rahm wrote: As I said, I was hoping to avoid rehashing this point, but the general consensus from the last rather contentious post [1] was that changing from the prevalent style of the codebase for primarily aesthetic reasons was hard to justify (points about

Re: Kris Maglione and Andrew McCreight are now XPConnect Peers

On 09/06/2017 07:47 PM, Bobby Holley wrote: XPConnect is not exactly a fun module. When I took the reins from mrbkap 4.5 years ago, Peter wiped a tear from his eye and said "Congratulations, Blake." Still, it's at the heart of Gecko, and needs ongoing attention from deep hackers. With the old

Re: Intent to ship: Abort API

I spoke with Ben yesterday and today and we decided that bug 1394102 should not block the shipping of this feature. That bug will be fixed as part of the Service Worker refactoring. Abort API and the Fetch() integration should be enabled by default in the next nightly. On Tue, Aug 29, 2017 at

Re: Firefox 55.* in Windows/Ubuntu - every day CPU 100%/Hangs Up. Please to do something!

Hi, if you could file a bug, we can try to figure this out: https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox=Untriaged Please attach the contents of about:support as an attachment, so we can get some idea of your configuration. Thanks, Panos On Wed, Sep 6, 2017 at 10:45 AM, Alexey

Re: Intent to ship: Abort API

On Wed, Sep 6, 2017 at 12:27 PM, Andrea Marchesini wrote: > Abort API and the Fetch() integration should be enabled by default in the > next nightly. > To clarify, its already enabled in nightly, but the patch to let it ride the trains is now in inbound. Thanks for

Device Memory header and JS API

Hi, I work on Chrome Web Platform and we just shipped an API for detecting Device Memory: header and JS API . Boris expressed

[no subject]

It's the weekly report on the state of triage in Firefox-related components. Marking Bugs for the Firefox 57 Release The bug that will overshadow all the hard work we put into the Firefox 57 release has probably already been filed. We need to find it and fix it. If you think a bug might affect

Intent to implement: RTCRtpTransceiver

    What: RTCRtpTransceiver is a central part of the w3c webrtc API (https://www.w3.org/TR/webrtc/) and JSEP spec (https://tools.ietf.org/html/draft-ietf-rtcweb-jsep). This is a significant addition to the webrtc API, and entails a rework of the internals (it is not practical to hide this

Re: Intent to implement: RTCRtpTransceiver

    That's right. Best regards, Byron Campen On 9/6/17 1:30 PM, Tom Ritter wrote: IIRC, the rework won't be able to be switched 'back-to-existing' with a pref, but we'll continue to respect existing disable-webrtc prefs and the --disable-webrtc compiler switch, right? -tom On Wed, Sep 6,

Re: Coding style: Placement of binary operators when breaking a long line

On Wed, Sep 6, 2017 at 7:18 PM, Mike Hommey wrote: > On a personal note, I find > 2000 as in the first sample more readable > than the latter. So much so that I'd actually prefer the logical > operators to be on the next line than boolean operator being on the > previous. A