MozillaZine

The first official 20171106 builds are out

Discussion about official Mozilla Firefox builds
Josa
 
Posts: 2713
Joined: July 28th, 2009, 4:52 pm

Post Posted November 5th, 2017, 7:20 am

Previous Nightly Builds thread 20171105

The first official 20171106 NIGHTLY builds are out
.The Official Firefox 57 RC1 builds are not yet out

Previous NIGHTLY: 20171105 (Fx 58.0a1)
Previous BETA: 20171103 (Fx 57.0b14)

Mozilla Inbound Builds
Treeherder
Release Notes: NIGHTLY | BETA
Changelogs: NIGHTLY | BETA


Fixed:
    NIGHTLY +6
  1. #1331209
  2. #1414147 [Core:CSS Parsing and Computation]-Move -moz-font-smoothing-background-color style struct storage from nsStyleUserInterface to nsStyleFont / nsFont [All][]
  3. #1414154 [Core:Graphics]-Store the font smoothing background color in ScaledFontMac instead of using GlyphRenderingOptions [All][]
  4. #1414157 [Core:Graphics: WebRender]-Pass the font smoothing background color to WebRender [Mac][[wr-reserve]]
  5. #1413867 [Core:JavaScript Engine]-Remove StopIteration [All][]
  6. #1414155 [Core:Memory Allocator]-Miscellaneous code changes related to size classes and constants/globals [Uns][]

    Partial Landings/Diagnostic Patches:
    None

    Beta 14 -> RC1 Changelog +1
  1. #1414416 [Firefox:Installer]-Backout bug 1413295 from 57 [Uns][]

Nightly 58 fixes since 20170921 (Gecko 57) ~2337
Beta 57 fixes since 20170802 (Gecko 56) ~3568

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide
Last edited by Josa on November 6th, 2017, 1:56 pm, edited 1 time in total.

tauio111
 
Posts: 17
Joined: August 12th, 2017, 8:52 am

Post Posted November 5th, 2017, 7:38 am

Lurtz wrote:It happens on both an Intel HD 520 and a Radeon R9 390 on Windows 10 16299.19.
It was worse, but after the fixes for the transparent rendering errors landed, it is better again, but still happening sometimes.

Yeah, It happened again on the newest build, no idea what triggers it. I do not remember it happening on Windows 7 (used a few days ago). Maybe it is something related to Radeon & Win10. Wouldn't know.

Omega X

User avatar
 
Posts: 7956
Joined: October 18th, 2007, 2:38 pm
Location: A Parallel Dimension...

Post Posted November 5th, 2017, 5:21 pm

There's definitely something going on with VP9 decode. Nightly is using double the CPU power than good builds at every quality level.
Latest: Firefox/57.0.2 *ESR/52.5 - Mobile/57.0.1 - Thunderbird/52.5 - SeaMonkey/2.49.1
Nightly: Nightly/59.0a1 - Mobile/59.0a1 - Daily/59.0a1 - SeaMonkey/2.55a1

sciguyryan
Folder@Home

User avatar
 
Posts: 2164
Joined: November 10th, 2004, 1:33 pm
Location: Wales

Post Posted November 6th, 2017, 12:28 am

Surprisingly I've been able to leave WebRender enabled for a few days without any crashes or severe issues. Performance is still a bit rough in some areas and the startup time is pretty bad... but it's much better than it was a few weeks ago.

Colour me impressed!
Visit My Blog if you want to hear more.

Ryan Jones

Lurtz
 
Posts: 219
Joined: June 12th, 2016, 12:25 pm

Post Posted November 6th, 2017, 1:12 am

Something's definitely off with VP9. Drops frames like crazy every few seconds. Maybe something to do with Media Cache off main thread?

sciguyryan wrote:Surprisingly I've been able to leave WebRender enabled for a few days without any crashes or severe issues. Performance is still a bit rough in some areas and the startup time is pretty bad... but it's much better than it was a few weeks ago.

Colour me impressed!

My thoughts exactly!

If scrolling performance would be en par with D3D11 Advanced Layers I would consider enabling it by default.

sciguyryan
Folder@Home

User avatar
 
Posts: 2164
Joined: November 10th, 2004, 1:33 pm
Location: Wales

Post Posted November 6th, 2017, 3:21 am

Lurtz wrote:My thoughts exactly!

If scrolling performance would be en par with D3D11 Advanced Layers I would consider enabling it by default.


It's interesting that you say that because I'm noticing times where scrolling performance is better with WebRender and Retain Display Lists enabled. The issue I see is consistency, some sites are awful, some are amazing. Still, not too shabby for a pre-alpha build.
Visit My Blog if you want to hear more.

Ryan Jones

Lurtz
 
Posts: 219
Joined: June 12th, 2016, 12:25 pm

Post Posted November 6th, 2017, 4:56 am

VP9 problems seem to be connected to this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1366201

WaltS48

User avatar
 
Posts: 3473
Joined: May 7th, 2010, 9:38 am
Location: Pennsylvania, USA

Post Posted November 6th, 2017, 7:11 am

Linux Nightly is out.

Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 ID:20171106100122
Linux Desktop - AMD Athlon(tm) II X3 455 3.3GHz | 8.0GB RAM | GeForce GT 630
Windows Notebook - AMD A8 7410 2.2GHz | 6.0GB RAM | AMD Radeon R5

tauio111
 
Posts: 17
Joined: August 12th, 2017, 8:52 am

Post Posted November 6th, 2017, 9:21 am

sciguyryan wrote:Surprisingly I've been able to leave WebRender enabled for a few days without any crashes or severe issues. Performance is still a bit rough in some areas and the startup time is pretty bad... but it's much better than it was a few weeks ago.

Colour me impressed!

Tried it again just now, the performance seems better than what it used to be, but I really fail to see the big difference between pre-webrender and webrender currently.
The scrolling performance on the other hand has gotten better now compared to how it was on Webrender not long ago.

The broken font anti-aliasing still plagues it. If you open up a screenshot and zoom in till you clearly see the pixels, you see that the fonts are anti-aliased in a BGR fashion (or so) instead of RGB. That is the reason for the blurry text. It should however be a very easy fix and I am pretty sure it is on their list.
Image

Enig123
 
Posts: 50
Joined: February 9th, 2006, 5:10 am

Post Posted November 6th, 2017, 10:24 am

Are there known problems with webrenderer of nightly on MacOS? I've seen scrolling lag when playing video on a website.

Or I should not enable webrenderer for MacOS?

Lurtz
 
Posts: 219
Joined: June 12th, 2016, 12:25 pm

Post Posted November 6th, 2017, 11:53 am

Wasn't the blurred RGB font problem fixed just a few days ago in WebRender?! Didn't that land in Nightly yet?

Mark12547
 
Posts: 143
Joined: May 13th, 2017, 11:36 am
Location: Oregon, United States, Earth

Post Posted November 6th, 2017, 12:22 pm

I thought Nightly was broken, but after trying Beta and Release with the same results, rebooting the modem, rebooting the PC, making sure the anti-virus is absolute current, checking most recent virus scan, it appears that the problem isn't Nightly.

Comcast is having backbone and DNS issues today that is affecting all "non-local" sites.

According to http://downdetector.com/status/comcast-xfinity the issues started about 1:04am EST.

ETA: backbone -> DNS (in bold area above) Nope, make that backbone and DNS issues.

ETA (12:19pm PST): The problem appears to be easing up some, but some areas are still reporting outages.
Last edited by Mark12547 on November 6th, 2017, 1:53 pm, edited 5 times in total.

Lurtz
 
Posts: 219
Joined: June 12th, 2016, 12:25 pm

Post Posted November 6th, 2017, 12:32 pm

Lurtz wrote:Wasn't the blurred RGB font problem fixed just a few days ago in WebRender?! Didn't that land in Nightly yet?

They just reopened that bug.

Josa
 
Posts: 2713
Joined: July 28th, 2009, 4:52 pm

Post Posted November 6th, 2017, 1:56 pm


bjherbison
 
Posts: 711
Joined: October 6th, 2003, 5:40 am
Location: Bolton, MA, US

Post Posted November 6th, 2017, 1:58 pm

Yeah, the Comcast issues hit just as I was reconfiguring the routers in my house. i was going crazy trying to get back to a stable environment before I realized the problem was outside my control.

Return to Firefox Builds


Who is online

Users browsing this forum: No registered users and 2 guests