I have triggered autoland in
https://bugzilla.mozilla.org/show_bug.cgi?id=1419277 to ship this to
release.
Also, as we only support macOS >= 10.9, I've removed a few
old/duplicated old font names from the default font list for zh
locales as well.
On Thu, Sep 7, 2017 at 4:11 PM, Tim Guan-tin Chien
This change is now on mozilla-inbound.
On Thursday, 9 November 2017 10:31:41 UTC, bo...@mozilla.com wrote:
> Hi,
>
> Early in the 59 cycle, I intend to make Windows 10 SDK version 10.0.14393 the
> minimum required for building Firefox.
>
> Like before, this is because of new Windows security f
For the next version of geckodriver I am intending that it not ship a Linux
32 bit version of Geckodriver. Currently it accounts of 0.1% of downloads
and we regularly get somewhat cryptic intermittents which are hard to
diagnose.
*What does this mean for most people?* We will be turning off the WD
Hi!
I made some crashes by hands (crashfirefox.exe) in Windows 7 and in Unix
through kill -ABRT
What are the symptoms? In random moments the Firefox v56.* has only-one
core CPU 100% eating. In Windows 7 (64bit) & Linux (Ubuntu 16.04 LTE 64bit)
Reports are here:
Ubuntu OS:
https://crash-stats.m
On 11/21/17 3:54 AM, Alexey Zvyagin wrote:
Hi!
I made some crashes by hands (crashfirefox.exe) in Windows 7 and in Unix
through kill -ABRT
What are the symptoms? In random moments the Firefox v56.* has only-one
core CPU 100% eating. In Windows 7 (64bit) & Linux (Ubuntu 16.04 LTE 64bit)
Reports
On Tue, Nov 21, 2017 at 5:25 AM, David Burns wrote:
> For the next version of geckodriver I am intending that it not ship a Linux
> 32 bit version of Geckodriver. Currently it accounts of 0.1% of downloads
> and we regularly get somewhat cryptic intermittents which are hard to
> diagnose.
>
I do
On Tue, Nov 21, 2017, at 06:54 AM, Alexey Zvyagin wrote:
> Hi!
>
> I made some crashes by hands (crashfirefox.exe) in Windows 7 and in Unix
> through kill -ABRT
>
> What are the symptoms? In random moments the Firefox v56.* has only-one
> core CPU 100% eating. In Windows 7 (64bit) & Linux (Ubuntu
On Tue, Nov 21, 2017 at 02:22:26PM -0500, Ted Mielczarek wrote:
On Tue, Nov 21, 2017, at 06:54 AM, Alexey Zvyagin wrote:
Hi!
I made some crashes by hands (crashfirefox.exe) in Windows 7 and in Unix
through kill -ABRT
What are the symptoms? In random moments the Firefox v56.* has only-one
core
Answered inline below.
On 21 November 2017 at 19:03, Nicholas Alexander
wrote:
>
>
> On Tue, Nov 21, 2017 at 5:25 AM, David Burns wrote:
>
>> For the next version of geckodriver I am intending that it not ship a
>> Linux
>> 32 bit version of Geckodriver. Currently it accounts of 0.1% of downloa
David,
On Tue, Nov 21, 2017 at 12:54 PM, David Burns wrote:
> Answered inline below.
>
> On 21 November 2017 at 19:03, Nicholas Alexander
> wrote:
>
>>
>>
>> On Tue, Nov 21, 2017 at 5:25 AM, David Burns wrote:
>>
>>> For the next version of geckodriver I am intending that it not ship a
>>> Lin
Is your profile local, or do you have it on a network share?
It's possible your db has some kind of corruption that causes
recursive references.
I'd first of all check it using sqlite3 and the PRAGMA integrity_check query.
If that passes (returns "ok"), I'd also try to run the Places
Maintenance f
Please file a bug for this issue, and we can take the discussion
there. This list isn't really the right place for it.
Thanks.
On Wed, Nov 22, 2017 at 12:27:09AM +0100, Marco Bonardo wrote:
Is your profile local, or do you have it on a network share?
It's possible your db has some kind of cor
I'm going to land a patch in
https://bugzilla.mozilla.org/show_bug.cgi?id=1414745 to make
nsBrowserStatusFilter::OnStateChange only deliver STATE_IS_NETWORK requests.
I noticed the mFinishedRequests / mTotalRequests counters used in
nsBrowserStatusFilter were buggy and ever since we applied the
13 matches
Mail list logo
