1895700 - Updating gets stuck at "Downloading update 0 bytes of 18.6MB"

Status: RESOLVED WORKSFORME

(Toolkit :: Application Update, defect)

Description

[Jeff Muizelaar [:jrmuizel]]

Here are the updater logs:

AUS:AUM AppUpdater:stop called
AUS:AUM AppUpdater:#awaitDownloadComplete - Download listener removed
AUS:AUM AppUpdater:#onException - Caught AbortError. Setting status NEVER_CHECKED
AUS:AUM AppUpdater:check - currentState=STATE_DOWNLOADING
AUS:AUM AppUpdater:check - downloading
AUS:SVC UpdateService:downloadUpdate - no support for downloading more than one update at a time
AUS:AUM AppUpdater:#awaitDownloadComplete - Registered download listener
AUS:AUM AppUpdater:#awaitDownloadComplete - Waiting for state transition.
AUS:AUM AppUpdater:stop called
AUS:AUM AppUpdater:#awaitDownloadComplete - Download listener removed
AUS:AUM AppUpdater:#onException - Caught AbortError. Setting status NEVER_CHECKED 

I had recently run another profile simultaneously and it showed an update being available so this may be related to that.

Comment 1

[Robin Steuber (she/her) [:bytesized]]

A couple of questions.

1. Can you still reproduce this problem?
2. What update channel are you on?
3. I notice that the log that you provide seems to loop. Is this because you checked for update multiple times? Is this the output from a single update check? Did it loop many times but you only copied a couple repetitions?
4. The title of this bug suggests that the UI gets stuck at "Downloading 0 bytes", is that right? The log ends with Setting status NEVER_CHECKED, which ought to show a "Check for Updates" button, so I'm surprised to hear that that is not the state that it ended in.
5. Could you check your update history? Are updates eventually getting installed (i.e. maybe just the UI is broken)? Or do updates never get installed?

Comment 2

[Jeff Muizelaar [:jrmuizel]]

(In reply to Robin Steuber (they/them) [:bytesized] from comment #1)

1. Can you still reproduce this problem?

Nope

2. What update channel are you on?

Nightly

3. I notice that the log that you provide seems to loop. Is this because you checked for update multiple times? Is this the output from a single update check? Did it loop many times but you only copied a couple repetitions?

I don't recall

4. The title of this bug suggests that the UI gets stuck at "Downloading 0 bytes", is that right? The log ends with Setting status NEVER_CHECKED, which ought to show a "Check for Updates" button, so I'm surprised to hear that that is not the state that it ended in.

That's correct.

5. Could you check your update history? Are updates eventually getting installed (i.e. maybe just the UI is broken)? Or do updates never get installed?

The problem went away after restarting Firefox.

Comment 3

[Robin Steuber (she/her) [:bytesized]]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #2)

(In reply to Robin Steuber (they/them) [:bytesized] from comment #1)

1. Can you still reproduce this problem?

Nope

Me neither. I guess I'll close this and we can reopen it if the problem reoccurs.

Comment 4

[Jeff Muizelaar [:jrmuizel]]

Does it make sense to add some logging so that if it happens again we'll be able to get the information we need to figure it out?

Comment 5

[Robin Steuber (she/her) [:bytesized]]

I'm not sure that there is something that I could add that would be both reasonable and useful. I'm a little baffled by the whole thing. I need to know why AppUpdater.stop() was called. But the thing is that presumably I do know. Outside of background tasks and testing, it's only called from here, which is only called from here, which is only called from here, the page's onUnload function.

And I really can't imagine a reason why that function would be called at this point. I'm really not sure what logging to even add. I'm suspicious that this would make more sense in the full context of exactly what actions resulted in this log.