The first official 20180312 builds are out

[Are You A Wiiizard?]

Mozilla would not fix
[*]#1386177 [Core:Audio/Video: Playback]-Very high memory usage after watching many HTML5 movies on Firefox, even after closing them all [Win]

Thanks for that bug.

Two perf profiles after skipping videos, seeking and skipping intros for ~20mins (no-where near as laggy as watching constantly for 2hrs+): https://perfht.ml/2DlPhrz

after restarting browser: https://perfht.ml/2HqYMIi

First profile is getting 8second BHR-detected hang / event processing delays. Performance degradation people are seeing might be because of this rather than a memory leak.

Memory leak doesn't seem to be the cause for me, is there any other bugs similar to what I'm seeing or will it need to be a new bug entirely?

[WaltS48]

Giggle. 59.0rc3 is out.

Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0 ID:20180310025718

[Tomatoshadow2]

Tab Warming was finally enabled by default for today's Nightly 61

Edit: And backed out again due to test failures...

Any idea, when they will try to put it back in? One of the features I'm looking forward to.

[Lurtz]

Any idea, when they will try to put it back in? One of the features I'm looking forward to.

Test failure is fixed, should be enabled in the next build.

[TheVisitor]

Any idea, when they will try to put it back in? One of the features I'm looking forward to.

Test failure is fixed, should be enabled in the next build.

That depends on 'if' the 'autoland' tree gets merged into m-c (mozilla-central) in time for tonight's Nightly.

EDIT: Autoland just merged into m-c and 'tab warming did not make it into tonight's Nightly...will have to see tomorrow if it makes it.

[DN123ABC]

Well, it did the auto-update, but no visible changes in version number.

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 ID:20180310025718

Here's to hoping for a solid update. Once the whole flipover thing to the newer version happens, I'll probably go on to the next version (60), but will back up profile first. The only thing really holding me back is lost session information until a new version of Session Manager comes out.

[WaltS48]

The 2nd Official 20180312 build is out.

Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 ID:20180312220041

[DN123ABC]

Wait, is Linux ahead of Windows? How'd you get 20180312 when mine only got 20180310 ?

[malliz]

From memory I think Linux compiles faster

[bjherbison]

Faster, yes, but not two days faster.

I just got the Linux update to Nightly 61.

[TheVisitor]

Nightly is out cset: https://hg.mozilla.org/mozilla-central/ ... 08d47f6621

I got a 17 meg partial.... hmmmm
Also 'Tab Warming' made it in today...

[Are You A Wiiizard?]

Latest update broke text rendering for me. Since text looked terrible I decided to try WR again (since the text was the major thing stopping me from testing) and OMG it's so much faster now (much faster than with WR disabled). Unfortunately it's text is still far worse than the currently broken text with WR disabled and scrolling is majorly broken along with random errors seen on pages.

[bjherbison]

The Linux update to the build for the 13th was only 8MB for me (a little larger than the last few).

I haven't noticed any text rendering issues.

[Mark12547]

I was viewing Google images (images.google.com), ended up scrolling to the very bottom for search term "emergency lighting led" (without quotes), and then when I moved to the top, the tab was blank! Then it took about a minute to reload the images.

Earlier today while scrolling down Google images it took about 20 seconds of 100% of one of the cores to finally pain the bottom half of the last row.

Whatever it is, this feels like it is a step backwards.

This is Firefox Nightly 61.0a1 (2018-03-13) (64-bit) Build-id 20180313100127 on Windows 7 (64-bit).

Anyone else experiencing something like this?

[TheVisitor]

I was viewing Google images (images.google.com), ended up scrolling to the very bottom for search term "emergency lighting led" (without quotes), and then when I moved to the top, the tab was blank! Then it took about a minute to reload the images.

Earlier today while scrolling down Google images it took about 20 seconds of 100% of one of the cores to finally pain the bottom half of the last row.

Whatever it is, this feels like it is a step backwards.

This is Firefox Nightly 61.0a1 (2018-03-13) (64-bit) Build-id 20180313100127 on Windows 7 (64-bit).

Anyone else experiencing something like this?

I believe I saw something similiar earlier today on FoxNews reading a story and opening the comments, suddenly scrolling via arrow-keys stopped, CPU spiked.
Scrolling with mouse-wheel still worked but scrolling up the page I saw various sections blank and would not fill in..continue scrolling up to top it was blank, but scrolling down again things began to fill in but still had hight CPU usage and arrow-keys still not work on that one page. Closed the tab I opened the story in and things have been OK so far.