1482218 - Shutdown hang preventing updates

Status: NEW

(Firefox :: General, defect, P5)

Description

[Mark Côté [:mcote]]

My Nightly install (on Windows 10) is currently stuck at 2018-08-06 (https://hg.mozilla.org/mozilla-central/rev/0dbeb72b579816a450db3430f35174655a975c53).  It is always prompting me to update, but always ends up at the same revision.

Note that something similar happened to me last week, but it fixed itself somehow.

bhearsum suggested enabling app.update.log, which I did, and here are the AUS:SVC lines from my browser console:

AUS:SVC Creating UpdateService
AUS:SVC readStatusFile - status: failed: 7, path: C:\Users\image\AppData\Local\Mozilla\updates\473384198A1E078D\updates\0\update.status
AUS:SVC isServiceInstalled - returning true
AUS:SVC shouldUseService - returning true
AUS:SVC getCanApplyUpdates - bypass the write checks because the Windows Maintenance Service can be used
AUS:SVC getCanStageUpdates - staging updates is disabled by preference app.update.staging.enabled
AUS:SVC isServiceInstalled - returning true
AUS:SVC Checker:getUpdateURL - update URL: https://aus5.mozilla.org/update/6/Firefox/63.0a1/20180806100140/WINNT_x86_64-msvc-x64/en-CA/nightly/Windows_NT%2010.0.0.0.17134.191%20(x64)(noBug1296630v1)(nowebsense)/ISET:SSE4_2,MEM:16231/default/default/update.xml
AUS:SVC UpdateService.canCheckForUpdates - able to check for updates
AUS:SVC Checker: checkForUpdates, force: false
AUS:SVC UpdateService.canCheckForUpdates - able to check for updates
AUS:SVC Checker:getUpdateURL - update URL: https://aus5.mozilla.org/update/6/Firefox/63.0a1/20180806100140/WINNT_x86_64-msvc-x64/en-CA/nightly/Windows_NT%2010.0.0.0.17134.191%20(x64)(noBug1296630v1)(nowebsense)/ISET:SSE4_2,MEM:16231/default/default/update.xml
AUS:SVC Checker:checkForUpdates - sending request to: https://aus5.mozilla.org/update/6/Firefox/63.0a1/20180806100140/WINNT_x86_64-msvc-x64/en-CA/nightly/Windows_NT%2010.0.0.0.17134.191%20(x64)(noBug1296630v1)(nowebsense)/ISET:SSE4_2,MEM:16231/default/default/update.xml
AUS:SVC Checker:onLoad - request completed downloading document
AUS:SVC Checker:onLoad - number of updates available: 1
AUS:SVC readStatusFile - status: failed: 7, path: C:\Users\image\AppData\Local\Mozilla\updates\473384198A1E078D\updates\0\update.status
AUS:SVC UpdateService.canCheckForUpdates - able to check for updates
AUS:SVC isServiceInstalled - returning true
AUS:SVC shouldUseService - returning true
AUS:SVC getCanApplyUpdates - bypass the write checks because the Windows Maintenance Service can be used
AUS:SVC readStatusFile - status: failed: 7, path: C:\Users\image\AppData\Local\Mozilla\updates\473384198A1E078D\updates\0\update.status

Comment 1

[Molly Howell (she/her) (mostly inactive)]

Thanks for the log output. What that shows is that updates are being detected and downloaded correctly, but failing to apply. The error code (7 == WRITE_ERROR) is a bit ambiguous, so it would help to also get the update.log file, which should be at the same path as the update.status file that the log above refers to (and possibly also last-update.log, which should be one directory up from there). Thanks.

Comment 2

[Mark Côté [:mcote]]

Attachment: last-update.log

Comment 3

[Mark Côté [:mcote]]

Hm, interestingly there is no update.log at C:\Users\image\AppData\Local\Mozilla\updates\473384198A1E078D\updates\0\.  The only files there are update.mar, update.status, and update.version.  I've attached last-update.log from C:\Users\image\AppData\Local\Mozilla\updates\473384198A1E078D\updates\.

Comment 4

[Mark Côté [:mcote]]

The problem just fixed itself after a reboot.  I'm starting to think it's something to do with my computer, which has been having some odd issues lately.  Feel free to close this out.

Comment 5

[Molly Howell (she/her) (mostly inactive)]

Thanks. The error in that last-update.log is that Firefox was still running when the updater started, which means it's hanging on shutdown. The updater tries its best to deal with that, but writing to an executable while it's running isn't possible on Windows. So the shutdown hang is the issue here, the update error is just a symptom of that. The hang could be either a legitimate Firefox bug or a transient problem caused by some other issue with the machine, but there's no way to tell without further investigation, so for now I'll just move this bug out of here rather than closing it.

Comment 6

[Sam Foster [:sfoster] (he/him)]

Taking a stab at a priority to move this out of the triage list. Adjust as necessary. Looks like the log has data we want to keep around in case we have similar reports.