The first official 20180121 builds are out

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

The first official 20180121 builds are out

Post by Josa »

Previous Nightly Builds thread 20180120

The first official 20180121 NIGHTLY builds are out
.The Official Firefox 58 RC7 builds are not yet out

Previous NIGHTLY: 20180120 (Fx 59.0a1)
Previous BETA: 20180119 (Fx 58.0 RC6)

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


Fixed:
  1. NIGHTLY +11
  2. #1431774 [Core:DOM]-Simplify some nsIImageLoadingContent bits [Uns][]
  3. #1430632 [Core:Graphics: Text]-DirectWrite support for OpenType Font Variations [Uns][]
  4. #1431726 [Core:JavaScript Engine]-Refactor GetBuiltinPrototype and friends [All][]
  5. #1431305 [Core:Layout: Text]-Wavy Dash doesn't fall back to "rotated" in vertical writing-mode [Uns][]
  6. #587523 [Core:Networking: HTTP]-Protect path of HTTP Referer Header when in Private Browsing [All][[necko-next]]
  7. #1419093 [Core:WebRTC]-Track RTC RTP source objects interface to dictionary spec change [Uns][]
  8. #1430213 [Core:WebRTC]-Pref toggle for RTCRtpReceiver getContributingSources and getSynchronizationSources APIs [Uns][]
  9. #1431841 [Firefox:Developer Tools: Inspector]-Show the flex lines in the flexbox highlighter [Uns][]
  10. #1431941 [Firefox:Developer Tools: Inspector]-Highlight flex-basis in the flexbox highlighter [Uns][]
  11. #1431947 [Firefox:Developer Tools: Inspector]-Remove the edge around the flex basis highlight [Uns][]
  12. #1420775 [Toolkit:Add-ons Manager]-Startup error; Undefined entity <menuitem class="pageActionContextMenuItem extensionUnpinned" [Uns][]
  1. Partial Landings/Diagnostic Patches:
    None
  1. RC6 -> RC7 Changelog +0
    None

Nightly 59 fixes since 20171113 (Gecko 58) ~2416
Beta 58 fixes since 20170921 (Gecko 57) ~2998

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide
Last edited by Josa on January 21st, 2018, 11:47 am, edited 1 time in total.
User avatar
geobomatic
Posts: 68
Joined: May 16th, 2015, 9:04 am

Re: The first official 20180121 builds are not yet out

Post by geobomatic »

Sorry if it has been asked but I couldn't find anything on the subject:
It seems I'm "losing the connection" on pages that I keep open all the time and need to refresh them to have them working again.
Ex: GMail, inoreader

Been like that for a over a week.
Is this a known bug?
DN123ABC
Posts: 695
Joined: January 9th, 2017, 10:10 am

Re: The first official 20180121 builds are not yet out

Post by DN123ABC »

Geobomatic wrote:Sorry if it has been asked but I couldn't find anything on the subject:
It seems I'm "losing the connection" on pages that I keep open all the time and need to refresh them to have them working again.
Ex: GMail, inoreader

Been like that for a over a week.
Is this a known bug?
Same here. It is also consuming ridiculous amounts of memory, to the point of stopping the entire computer.

I only have 2 windows open, with 41 tabs in total. No extensions running.

It also won't update the "Beta" version.

Version:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0 ID:20180118215408
User avatar
Snake4
Posts: 1841
Joined: December 27th, 2017, 4:03 am
Location: Australia

Re: The first official 20180121 builds are not yet out

Post by Snake4 »

DN123ABC wrote:
Geobomatic wrote:Sorry if it has been asked but I couldn't find anything on the subject:
It seems I'm "losing the connection" on pages that I keep open all the time and need to refresh them to have them working again.
Ex: GMail, inoreader

Been like that for a over a week.
Is this a known bug?
Same here. It is also consuming ridiculous amounts of memory, to the point of stopping the entire computer.

I only have 2 windows open, with 41 tabs in total. No extensions running.

It also won't update the "Beta" version.

Version:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0 ID:20180118215408
because there is NO Beta to update to. the Dev Edition is 59.0b1 , the DevEdition is NOT Beta. i guess you could say 58 is still on the Beta channel since it hasnt been up dated to 59 https://wiki.mozilla.org/RapidRelease/Calendar
Nightly Blog
Release Calendar
Posted With Chrome Or Firefox
DN123ABC
Posts: 695
Joined: January 9th, 2017, 10:10 am

Re: The first official 20180121 builds are not yet out

Post by DN123ABC »

OK, this makes sense I guess. So, version 58 is stuck in limbo for a while?
TheVisitor
Posts: 5469
Joined: May 13th, 2012, 10:43 am

Re: The first official 20180121 builds are not yet out

Post by TheVisitor »

DN123ABC wrote:OK, this makes sense I guess. So, version 58 is stuck in limbo for a while?
See the release calendar: https://wiki.mozilla.org/RapidRelease/Calendar

58 goes Release on 1/22 - then a day or so later, perhaps same day, beta channel will move to '59'
Lurtz
Posts: 359
Joined: June 12th, 2016, 12:25 pm

Re: The first official 20180121 builds are not yet out

Post by Lurtz »

DN123ABC wrote:OK, this makes sense I guess. So, version 58 is stuck in limbo for a while?
58 Beta now gets the stabilization phase leading up to the release of 58. They have to test crash rates for 58 release candidates on some population anyway ;)
59 gets two betas in DevEdition, then 59 Beta 3 is released in Beta channel (next Wednesday).
tauio111
Posts: 18
Joined: August 12th, 2017, 8:52 am

Re: The first official 20180121 builds are not yet out

Post by tauio111 »

I've been running on WR for the past few days without any of the red flickering happening anymore. Which is nice.
I only had a slight text corruption issue for a tad bit after having the browser open for a few hours.

However, WR does not feel any faster nor slower to me than the old render pipeline. about:support indicates that WR is in use.
Hope it turns fast after they remove the debug stuff from it after its finished.
Lurtz
Posts: 359
Joined: June 12th, 2016, 12:25 pm

Re: The first official 20180121 builds are not yet out

Post by Lurtz »

WebRender is not so much about being faster than about achieving a more consistent rendering performance, especially on high resolution screens or in intense applications like VR.
ashleylai87
Posts: 218
Joined: December 13th, 2013, 7:40 pm

Re: The first official 20180121 builds are not yet out

Post by ashleylai87 »

Quick question...

This one is safe.....or is it bad?

disable-js-shared-memory@mozilla.org.xpi
User avatar
RedSign
Posts: 88
Joined: April 12th, 2008, 2:13 pm

Re: The first official 20180121 builds are not yet out

Post by RedSign »

Lurtz wrote:WebRender is not so much about being faster than about achieving a more consistent rendering performance, especially on high resolution screens or in intense applications like VR.
Source? Fx needs better performance in graphics especially for users with high resolutions, imho. If there is a chance to get a superior performance in some configurations then go for it even if the performance on other configurations isn't that good and is therefore 'inconsistent'. I don't understand how consistency should be a factor in rendering performance. The rendering performance should be as good as possible on any given system, shouldn't it?
Josa
Posts: 7360
Joined: July 28th, 2009, 4:52 pm

Re: The first official 20180121 builds are not yet out

Post by Josa »

ashleylai87 wrote:Quick question...

This one is safe.....or is it bad?

disable-js-shared-memory@mozilla.org.xpi
Temporary mitigation for Spectre
Josa
Posts: 7360
Joined: July 28th, 2009, 4:52 pm

Re: The first official 20180121 builds are out

Post by Josa »

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

Re: The first official 20180121 builds are not yet out

Post by Lurtz »

RedSign wrote:Source? Fx needs better performance in graphics especially for users with high resolutions, imho. If there is a chance to get a superior performance in some configurations then go for it even if the performance on other configurations isn't that good and is therefore 'inconsistent'. I don't understand how consistency should be a factor in rendering performance. The rendering performance should be as good as possible on any given system, shouldn't it?
Lin Clark explained it here:
https://hacks.mozilla.org/2017/10/the-w ... d-of-jank/
Locked