The first official 20181231 builds are out

[Josa]

Previous Nightly Builds thread 20181230

The first official 20181231 NIGHTLY builds are out
.The Official Firefox 65 Beta 8 builds are not yet out

Previous NIGHTLY: 20181230 (Fx 66.0a1)
Previous BETA: 20181228 (Fx 65.0b7)

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


Fixed:

1. NIGHTLY +2
2. #1513934 [Core:JavaScript: Internationalization API]-Import patch for ICU-20302 [Uns][]
3. #1472557 [Toolkit:XUL Widgets]-Remove the "scrollbox" anonymous element from "richlistbox" [Uns][]

1. Partial Landings/Diagnostic Patches:
2. #1516727 [Core:SVG]-Having classes called SVGAngle and nsSVGAngle is confusing [All][]

1. Beta 7 -> Beta 8 Changelog +3
2. #1505250 [Core:Audio/Video: Playback]-Intermittent dom/media/test/test_looping_eventsOrder.html | application crashed [@ mozilla::MediaDecoderStateMachine::LoopingDecodingState::HandleError(mozilla::MediaResult const&)] after Assertion failure: aError != NS_ERROR_DOM_MEDIA_END_OF_STREAM [Uns][]
3. #1511235 [Core:Audio/Video: Playback]-invisible video decoding causes high CPU usage [Uns][[webcompat]]
4. #1512597 [Core:CSS Parsing and Computation]-SVG fill: currentColor is incorrect if parent is an a:visited element [All][]

Nightly 66 fixes since 20181210 (Gecko 65) ~630
Beta 65 fixes since 20181022 (Gecko 64) ~2169

Nightly Blog
Release Calendar
Release Tracking
MozRegression Guide

[TheVisitor]

I just got a full push on today's Nightly...

[Mark12547]

I just got a full push on today's Nightly...

I saw two pushes when I went into Help -> About Nightly, and the Options -> "General" tab -> "Nightly Updates" section -> "Show update history" confirmed it. In chronological order:

Nightly 66.0a1 (20181231091417)
Installed on: December 31, 2018, 9:04:12 AM

Status: The Update could not be installed (patch apply failed)

followed 15 seconds later by

Nightly 66.0a1 (20181231091417)
Installed on: December 31, 2018, 9:04:27 AM

Status: The Update was sucessfully installed

For whatever it's worth, this seems to be the relevant section of the updates.xml:

Code: Select all

<updates><update appVersion="66.0a1" buildID="20181231091417" channel="nightly" displayVersion="66.0a1" installDate="1546275867026" isCompleteUpdate="true" name="Nightly 66.0a1" promptWaitTime="43200" serviceURL="https://aus5.mozilla.org/update/6/Firefox/66.0a1/20181230093119/WINNT_x86_64-msvc-x64/en-US/nightly/Windows_NT%2010.0.0.0.17134.472%20(x64)/ISET:SSE4_2,MEM:12168/default/default/update.xml?force=1" type="minor" detailsURL="https://www.mozilla.org/en-US/firefox/nightly/notes/" previousAppVersion="66.0a1" statusText="The Update was successfully installed" platformVersion="66.0a1" foregroundDownload="true" patchingFailed="partial" stagingFailed="true"><patch finalURL="https://archive.mozilla.org/pub/firefox/nightly/2018/12/2018-12-31-09-14-17-mozilla-central/firefox-66.0a1.en-US.win64.complete.mar" selected="true" size="50725321" state="succeeded" type="complete" URL="https://archive.mozilla.org/pub/firefox/nightly/2018/12/2018-12-31-09-14-17-mozilla-central/firefox-66.0a1.en-US.win64.complete.mar"/><patch errorCode="4" finalURL="https://archive.mozilla.org/pub/firefox/nightly/partials/2018/12/2018-12-31-09-14-17-mozilla-central/firefox-mozilla-central-66.0a1-win64-en-US-20181230093119-20181231091417.partial.mar" size="5485327" state="failed" type="partial" URL="https://archive.mozilla.org/pub/firefox/nightly/partials/2018/12/2018-12-31-09-14-17-mozilla-central/firefox-mozilla-central-66.0a1-win64-en-US-20181230093119-20181231091417.partial.mar"/></update>
<update appVersion="66.0a1" buildID="20181231091417" channel="nightly" displayVersion="66.0a1" installDate="1546275852201" isCompleteUpdate="true" name="Nightly 66.0a1" promptWaitTime="43200" serviceURL="https://aus5.mozilla.org/update/6/Firefox/66.0a1/20181230093119/WINNT_x86_64-msvc-x64/en-US/nightly/Windows_NT%2010.0.0.0.17134.472%20(x64)/ISET:SSE4_2,MEM:12168/default/default/update.xml?force=1" type="minor" detailsURL="https://www.mozilla.org/en-US/firefox/nightly/notes/" previousAppVersion="66.0a1" statusText="The Update could not be installed (patch apply failed)" platformVersion="66.0a1" foregroundDownload="true" patchingFailed="partial" stagingFailed="true"><patch finalURL="https://archive.mozilla.org/pub/firefox/nightly/2018/12/2018-12-31-09-14-17-mozilla-central/firefox-66.0a1.en-US.win64.complete.mar" selected="true" size="50725321" state="downloading" type="complete" URL="https://archive.mozilla.org/pub/firefox/nightly/2018/12/2018-12-31-09-14-17-mozilla-central/firefox-66.0a1.en-US.win64.complete.mar"/><patch errorCode="4" finalURL="https://archive.mozilla.org/pub/firefox/nightly/partials/2018/12/2018-12-31-09-14-17-mozilla-central/firefox-mozilla-central-66.0a1-win64-en-US-20181230093119-20181231091417.partial.mar" size="5485327" state="failed" type="partial" URL="https://archive.mozilla.org/pub/firefox/nightly/partials/2018/12/2018-12-31-09-14-17-mozilla-central/firefox-mozilla-central-66.0a1-win64-en-US-20181230093119-20181231091417.partial.mar"/></update>

[Mark12547]

Tonight's patch to buildID="20181231212755" was 5MB, so hopefully this morning's grabbing the 5MB partial then grabbing the 50MB full was just a one-time fluke, though if this is Bug 1505964 we may be seeing it again.

[Jgr9]

Has Nightly become extremely slow to start recently or do I need to check my addons?

[streetwolf]

Has Nightly become extremely slow to start recently or do I need to check my addons?

WFM. Of course you've already tried safe mode and/or a new profile

[Mark12547]

Has Nightly become extremely slow to start recently or do I need to check my addons?

One thing I learned on my new machine (Windows 10, 12 GB RAM) is that if I have the antivirus do a full system scan, the disk cache gets wiped out in the process since all of the useful cached files had been replaced by what the antivirus most recently read. But the second Firefox restart is back to its fairly speedy self.

[Josa]

This thread is closed, please use the next one.