The first official 20180213 builds are out

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

The first official 20180213 builds are out

Post by Josa »

Previous Nightly Builds thread 20180212

The first official 20180213 NIGHTLY builds are out
The Official Firefox 59 Beta 9 builds are out

Previous NIGHTLY: 20180212 (Fx 60.0a1)
Previous BETA: 20180209 (Fx 59.0b8)

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


Fixed:
  1. NIGHTLY +58
  2. #1436983
  3. #1182329 [Core:Audio/Video: Playback]-WebRTC streams should be able to be automatically played even with media.autoplay.enabled=false [Uns][]
  4. #1437655 [Core:CSS Parsing and Computation]-nsRuleNode.cpp:2886:10: warning: 'return' will never be executed [-Wunreachable-code-return] [Uns][]
  5. #1394233 [Core:CSS Parsing and Computation]-stylo: [non-e10s] Certain rule in userContent.css is not applied [Uns][]
  6. #1437616 [Core:DOM: Device Interfaces]-Use proper WebAuthn result types defined in the .pidl [Uns][]
  7. #1437487 [Core:DOM: Device Interfaces]-[u2f-hid-rs] Allow passing an empty key handles list [Uns][]
  8. #1429286 [Core:DOM: Push Notifications]-Extend push and notification telemetry [All][]
  9. #1437188 [Core:DOM]-14,000 fetch related warnings during testing on linux64 debug [Uns][]
  10. #1437255 [Core:DOM]-@@unscopable value objects in the DOM should have a null prototype [Uns][]
  11. #1437680 [Core:DOM]-Avoid assertions in dom/tests/mochitest/general/test_contentViewer_overrideDPPX.html with the patch for bug 1193394 [Uns][]
  12. #1026714 [Core:DOM]-Don't mark nodes in the shadow tree as orphan nodes [All][]
  13. #1436744 [Core:DOM]-Get rid of WorkerCheckAPIExposureOnMainThreadRunnable [Uns][]
  14. #1435296 [Core:DOM]-Reduce Timer Resolution to 2ms [Uns][]
  15. #830221 [Core:DOM]-Remove nsIDOMDOMImplementation [All][]
  16. #1437362 [Core:DOM]-remove nsIDOMWindowUtils.focus [Uns][]
  17. #1431404 [Core:Disability Access APIs]-Crash in mozilla::mscom::Interceptor::GetInitialInterceptorForIID [Win][]
  18. #785440 [Core:Gecko Profiler]-Support profiling DOM calls in the profiler [Mac][]
  19. #1434965 [Core:Gecko Profiler]-UniqueStacks holds on to the JSContext pointer for too long [Uns][]
  20. #1436058 [Core:Graphics: WebRender]-Update webrender to 342bc314db94aa439b2001249c5f24ccfcbccc22 [Uns][[gfx-noted]]
  21. #1432375 [Core:Graphics: WebRender]-image.mem.shared: black bookmarks folder [Lin][]
  22. #1435938 [Core:Graphics]-Add basic logging for DrawTargetCapture [Uns][[gfx-noted]]
  23. #1430897 [Core:Graphics]-Revisit CONTENT_LARGE_PAINT_PHASE_WEIGHT [Uns][]
  24. #1437125 [Core:JavaScript Engine]-ASan heap-buffer-overflow within GET_UINT32_INDEX | js::jit::IonBuilder::inspectOpcode [JSOP_DEFFUN] [Uns][]
  25. #1436773 [Core:JavaScript Engine]-Initialize LifoAlloc memory to some non-zero value when reserved [Uns][]
  26. #1436697 [Core:JavaScript: GC]-Heap growth factor limits are too low [Uns][]
  27. #1436535 [Core:Layout: Text]-Normal weight font does not fallback to its variant when character is missing, but non-normal one will [Uns][]
  28. #1435650 [Core:Layout: Web Painting]-Avoid calling GetOffsetToCrossDoc during ProcessDisplayItems [Uns][]
  29. #1429932 [Core:Layout: Web Painting]-Don't build layers if the display list hasn't changed [Uns][]
  30. #1435649 [Core:Layout: Web Painting]-Don't touch the display item when taking the early return in ComputeGeometryChangeForItemW [Uns][]
  31. #1436189 [Core:Layout: Web Painting]-Marking the frame's overflow area for rebuild doesn't include out-of-flow descendants [Uns][]
  32. #1435643 [Core:Layout: Web Painting]-Remove layer flattening code [Uns][]
  33. #1437625 [Core:Layout: Web Painting]-nsCSSRenderingBorders.cpp calls two static functions from nsCSSRendering.cpp (and depends on fragile unified build grouping to call them) [Uns][]
  34. #1420480 [Core:Layout: Web Painting]-regression: CSS Menus layering under other page elements. [All][]
  35. #1437599 [Core:Layout]-Build warning: nsFrame.cpp:1903:10: warning: 'return' will never be executed [-Wunreachable-code-return] [Uns][]
  36. #1237454 [Core:Layout]-[Power] Optimize animations in visibility:hidden elements [All][[Power:P1][platform][qf:investigate]]
  37. #1437058 [Core:Networking: Cache]-Add CacheEntryHandle::~CacheEntryHandle log [Uns][[necko-triaged]]
  38. #1437513 [Core:Networking: HTTP]-Http2Session::RecvPushPromise: let push through for OnPush [Uns][[necko-triaged]]
  39. #1437152 [Core:Networking]-NS_ReadInputStreamToString completely ignores the passed-in string's capacity [All][[necko-triaged][MemShrink]]
  40. #1436643 [Core:Preferences: Backend]-Use a PLDHashTable `initEntry` function for Pref. [Uns][]
  41. #1436948 [Core:Security: PSM]-Update cbor lib [Uns][]
  42. #1436902 [Core:XPCOM]-Consider a version of NS_DECL_ISUPPORTS_INHERITED that has 0 overhead when built without refcount logging [Uns][]
  43. #1437114 [Core:XPCOM]-Crash in mozilla::ipc::ProcessLink::SendMessageW | IPC_Message_Name=PExternalHelperApp::Msg_OnDataAvailable [Win][]
  44. #1437604 [Core:XPCOM]-remove NS_INTERFACE_MAP_END_THREADSAFE [All][]
  45. #1436150 [Firefox:Developer Tools: Debugger]-Make debugger-controller.js properly handle watch expressions, containing syntax errors, where the error message for the syntax error contains U+0022 QUOTATION MARK within it [All][]
  46. #1430919 [Firefox:Developer Tools: Inspector]-Enable writing mode / RTL support for Grid Inspector [All][[designer-tools]]
  47. #1430918 [Firefox:Developer Tools: Inspector]-Rotate grid outline in Layout panel when writing modes / RTL are used [All][[designer-tools]]
  48. #1426482 [Firefox:General]-Collect chrome JS errors in Nightly [Uns][]
  49. #1437486 [Firefox:General]-Forget about site no longer clears anything but 5 minute intervals on Nightly [Uns][]
  50. #1433511 [Firefox:Site Identity and Permission Panels]-Website with DENY permission for popups still shows up as "Allow" in the Permissions Panel [Uns][]
  51. #1436351 [Firefox:Tabbed Browser]-JavaScript error: chrome://browser/content/tabbrowser.xml, line 2473: TypeError: cannot use 'in' operator to search for 'canGoBack' in 'browser' [All][]
  52. #1436445 [Release Engineering:Release Automation]-Use correct icon for Firefox Snap [Uns][]
  53. #1437431 [Toolkit:Autocomplete]-Adjust the accessible role for the PopupAutoCompleteRichResult panel to not be a menu [All][]
  54. #1407693 [Toolkit:Crash Reporting]-Don't attempt to create a file on crash in content process [All][]
  55. #1337869 [Toolkit:Find Toolbar]-modalRepaintScheduler is too slow [Uns][]
  56. #1437096 [Toolkit:Places]-Remove deprecated nsIFile arguments to importFromFile/exportFromFile in Bookmark HTML/JSON code [Uns][[fxsearch]]
  57. #1437040 [Toolkit:Places]-Remove synchronous Bookmarks::GetItemIndex [Uns][]
  58. #1432791 [Toolkit:Telemetry]-Can we remove the Microsecond AutoTimer resolution? [Uns][[lang=c++][good-next-bug]]
  59. #1427945 [Toolkit:WebPayments UI]-Implement a Payment Request Shipping Option Picker [All][]
  1. Partial Landings/Diagnostic Patches:
  2. #1434429 [Core:JavaScript Engine]-More rounds of TokenStream adjustments for UTF-8 tokenizing/parsing [All][]
  3. #1422043 [Core:JavaScript Engine: JIT]-wasm: Lazy entry stub generation for function tables [Uns][]
  4. #1425580 [Core:JavaScript Engine: JIT]-Consider devirtualizing LIR [All][]
  5. #1428453 [Core:JavaScript Engine: JIT]-Baldr: switch traps to use actual hardware traps [Uns][]
  1. Beta 8 -> Beta 9 Changelog +6
  2. #1429768
  3. #1434969 [Core:Editor]-Too many warnings: 'mOffset.value() >= mParent->Length()' (EditorDOMPoint.h, line 500) and '!mParent || mOffset.value() <= mParent->Length()' (EditorDOMPoint.h, line 373)) [Uns][]
  4. #1436216 [Core:Editor]-Too many warnings: '!mParent || mOffset.value() <= mParent->Length()' (EditorDOMPoint.h, line 373)) [All][]
  5. #1430761 [Core:JavaScript: Internationalization API]-Update to tzdata2018c [Uns][]
  6. #1436445 [Release Engineering:Release Automation]-Use correct icon for Firefox Snap [Uns][]
  7. #1423762 [Toolkit:WebExtensions: Frontend]-Rename toolbar_vertical_separator to toolbar_field_separator [Uns][]

Nightly 60 fixes since 20180122 (Gecko 59) ~865
Beta 59 fixes since 20171113 (Gecko 58) ~2511

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide
Last edited by Josa on February 13th, 2018, 9:15 am, edited 1 time in total.
User avatar
smsmith
Moderator
Posts: 19979
Joined: December 7th, 2004, 8:51 pm
Location: Indiana

Re: The first official 20180213 builds are not yet out

Post by smsmith »

The Tinsmith wrote:
Mark12547 wrote:
The Tinsmith wrote:If one is not sitting and watching how could I find out what the size of the update(s) installed was?
The updates arrive more frequently at 7am & 7pm my time than at other times, so near those times I do Help -> About Nightly and if it triggers the download of the update it shows the size.

Hmm...I was hoping for an app or a log file.
I'm not certain the answer you are looking for will be there, but poking around on my system, I found a file called updates.xml in a randomly named folder at:
C:\Users\[windowsID]\AppData\Local\Mozilla\updates\thisistherandomfolder\updates.xml

The file appears to contain info about the last ten updates.

Code: Select all

<update xmlns="http://www.mozilla.org/2005/app-update" platformVersion="60.0a1" statusText="The Update was successfully installed" previousAppVersion="60.0a1" detailsURL="https://www.mozilla.org/en-US/firefox/nightly/notes/" type="minor" serviceURL="https://aus5.mozilla.org/update/6/Firefox/60.0a1/20180212100154/WINNT_x86_64-msvc-x64/en-US/nightly/Windows_NT%2010.0.0.0.16299.214%20(x64)(noBug1296630v1)(nowebsense)/ISET:SSE4_2,MEM:8079/default/default/update.xml" promptWaitTime="43200" name="Nightly 60.0a1" isCompleteUpdate="false" installDate="1518489806879" displayVersion="60.0a1" channel="nightly" buildID="20180212220112" appVersion="60.0a1">
<patch type="complete" URL="https://archive.mozilla.org/pub/firefox/nightly/2018/02/2018-02-12-22-01-12-mozilla-central/firefox-60.0a1.en-US.win64.complete.mar" state="null" size="45333147"/>
<patch type="partial" URL="https://archive.mozilla.org/pub/firefox/nightly/partials/2018/02/2018-02-12-22-01-12-mozilla-central/firefox-mozilla-central-60.0a1-win64-en-US-20180212100154-20180212220112.partial.mar" state="succeeded" size="40299558" entityID="%229c954e7976b344d1f76f83b9692d2115%22/40299558/Tue, 13 Feb 2018 00:57:05 GMT" selected="true"/>
</update>
I'm fairly certain my last ten or so updates have been partials, which makes sense since they all list state="succeeded" in the partial patch type and isCompleteUpdate="false". Note the "size" information, which appears to be bytes.
Give a man a fish, and he eats for a day. Teach a man to fish, and he eats for a lifetime.
I like poetry, long walks on the beach and poking dead things with a stick.
Please do not PM me for personal support. Keep posts here in the Forums instead and we all learn.
bjherbison
Posts: 1039
Joined: October 6th, 2003, 5:40 am
Location: Bolton, MA, US
Contact:

Re: The first official 20180213 builds are not yet out

Post by bjherbison »

updates.xml is a good find for researching whether previous builds have been full or partial, at least on Windows. I can't find an equivalent file on Linux.

You are correct, the size is bytes.
https://wiki.mozilla.org/Software_Updat ... xml_Format
User avatar
smsmith
Moderator
Posts: 19979
Joined: December 7th, 2004, 8:51 pm
Location: Indiana

Re: The first official 20180213 builds are not yet out

Post by smsmith »

I'm getting a pretty instantaneous crash using the 02/13 build. I even downloaded a full copy thinking the update might have been bad. Still yet to try safe mode.

EDIT: Crashes even faster in safe mode. :(
Give a man a fish, and he eats for a day. Teach a man to fish, and he eats for a lifetime.
I like poetry, long walks on the beach and poking dead things with a stick.
Please do not PM me for personal support. Keep posts here in the Forums instead and we all learn.
bjherbison
Posts: 1039
Joined: October 6th, 2003, 5:40 am
Location: Bolton, MA, US
Contact:

Re: The first official 20180213 builds are not yet out

Post by bjherbison »

Hopefully there are crash reports to submit a bug.

(I have not seen any crashes with the Nightly for the 13th, and I've visited a wide variety of pages.
User avatar
WaltS48
Posts: 5141
Joined: May 7th, 2010, 9:38 am
Location: Pennsylvania, USA

Re: The first official 20180213 builds are not yet out

Post by WaltS48 »

bjherbison wrote:updates.xml is a good find for researching whether previous builds have been full or partial, at least on Windows. I can't find an equivalent file on Linux.

You are correct, the size is bytes.
https://wiki.mozilla.org/Software_Updat ... xml_Format
The equivalent file is in the application folder. My Nightly is in ~/Apps/firefox/fxnightly.

Today's update information.

Code: Select all

<update appVersion="60.0a1" buildID="20180213100127" channel="nightly" displayVersion="60.0a1" installDate="1518526904591" isCompleteUpdate="false" name="Nightly 60.0a1" promptWaitTime="43200" serviceURL="https://aus5.mozilla.org/update/6/Firefox/60.0a1/20180212220112/Linux_x86_64-gcc3/en-US/nightly/Linux%204.4.0-112-generic%20(GTK%203.18.9%2Clibpulse%208.0.0)/ISET:SSE3,MEM:7981/default/default/update.xml?force=1" type="minor" detailsURL="https://www.mozilla.org/en-US/firefox/nightly/notes/" previousAppVersion="60.0a1" statusText="The Update was successfully installed" platformVersion="60.0a1" foregroundDownload="true"><patch size="51039610" state="null" type="complete" URL="https://archive.mozilla.org/pub/firefox/nightly/2018/02/2018-02-13-10-01-27-mozilla-central/firefox-60.0a1.en-US.linux-x86_64.complete.mar"/><patch selected="true" size="44254103" state="succeeded" type="partial" URL="https://archive.mozilla.org/pub/firefox/nightly/partials/2018/02/2018-02-13-10-01-27-mozilla-central/firefox-mozilla-central-60.0a1-linux-x86_64-en-US-20180212220112-20180213100127.partial.mar" entityID="%22b8c3e0bd775842739fd22f77e474e804%22/44254103/Tue, 13 Feb 2018 11:40:16 GMT"/></update>
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
knowguy
Posts: 5
Joined: February 13th, 2018, 8:01 am

Re: The first official 20180213 builds are not yet out

Post by knowguy »

Can someone tell me in what nightly this bug is fixed? And how do I tell with future big fixes?
https://bugzilla.mozilla.org/show_bug.cgi?id=1420480
TheVisitor
Posts: 5472
Joined: May 13th, 2012, 10:43 am

Re: The first official 20180213 builds are not yet out

Post by TheVisitor »

knowguy wrote:Can someone tell me in what nightly this bug is fixed? And how do I tell with future big fixes?
https://bugzilla.mozilla.org/show_bug.cgi?id=1420480
Looks like it landed in the 2nd Nightly on the 12th, so should definitely be in today's. They added a test so Mozilla test structure should find this should it occur again.
bjherbison
Posts: 1039
Joined: October 6th, 2003, 5:40 am
Location: Bolton, MA, US
Contact:

Re: The first official 20180213 builds are not yet out

Post by bjherbison »

Thanks! Found it.

To answer the question asked a couple of days ago, my morning patch on 9 February ("2018-02-09-00-56-28-mozilla-central") used a full ("complete") update, but the last nine updates have been partial. I don't remember anything strange in my computer use on the 8th/9th which would have caused a complete update.
User avatar
smsmith
Moderator
Posts: 19979
Joined: December 7th, 2004, 8:51 pm
Location: Indiana

Re: The first official 20180213 builds are not yet out

Post by smsmith »

bjherbison wrote:Hopefully there are crash reports to submit a bug.

(I have not seen any crashes with the Nightly for the 13th, and I've visited a wide variety of pages.
Works in a new profile. Sigh.
Give a man a fish, and he eats for a day. Teach a man to fish, and he eats for a lifetime.
I like poetry, long walks on the beach and poking dead things with a stick.
Please do not PM me for personal support. Keep posts here in the Forums instead and we all learn.
OllyHodgson
Posts: 2
Joined: June 20th, 2012, 3:33 am

Re: The first official 20180213 builds are not yet out

Post by OllyHodgson »

smsmith wrote:
bjherbison wrote:Hopefully there are crash reports to submit a bug.

(I have not seen any crashes with the Nightly for the 13th, and I've visited a wide variety of pages.
Works in a new profile. Sigh.
From the 20-something crash reports my machine sent, it seems to be a WebRender thing. New profile has it switched off by default.
Josa
Posts: 7398
Joined: July 28th, 2009, 4:52 pm

Re: The first official 20180213 builds are out

Post by Josa »

Locked