1035098 - First Loop call after upgrade fails

Status: RESOLVED WORKSFORME

(Hello (Loop) :: Client, defect)

Description

[Romain Testard [:RT]]

Attachment: Browser console log on link generator side

Link generator: FF Nightly on last update running on Windows 8
Link clicker: Firefox 30 on Windows 7

I noticed on the last few nightly upgrades that the first call made after a nightly upgrade always does the following: as the link clicker clicks no notification is received on the link generator side.

Comment 1

[Romain Testard [:RT]]

Attachment: about:webrtc on link clicker side

Comment 2

[Romain Testard [:RT]]

Attachment: Web Console log on link clicker side

Comment 3

[Romain Testard [:RT]]

If I restart the browser, the link generated which failed at first browser launch now works fine.
All new links generated then work as expected.

Comment 4

[Mark Banner (:standard8)]

Taking to remind me to keep an eye out for this.

One question, is the link generated before, or after, the nightly upgrade?

Comment 5

[Romain Testard [:RT]]

The link is generated after the nightly upgrade.
The error in the browser log (link generator) appeared as I clicked the link on the clicker side:
"getLoopCharPref had trouble getting seenToS; exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: resource:///modules/loop/MozLoopService.jsm :: this.MozLoopService.getLoopCharPref :: line 485"  data: no]" MozLoopService.jsm:487

Comment 6

[Mark Banner (:standard8)]

(In reply to Romain Testard [:RT] from comment #5)
> The link is generated after the nightly upgrade.

Ok, that's a bit stranger. It suggests the websocket wasn't set up fully when it should have been.

> The error in the browser log (link generator) appeared as I clicked the link
> on the clicker side:
> "getLoopCharPref had trouble getting seenToS; exception: [Exception...
> "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED)
> [nsIPrefBranch.getCharPref]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" 
> location: "JS frame :: resource:///modules/loop/MozLoopService.jsm ::
> this.MozLoopService.getLoopCharPref :: line 485"  data: no]"
> MozLoopService.jsm:487

This would have actually been when opening the panel for the first time for the display of the new ToS. It is actually harmless, although it does get logged.

Comment 7

[Romain Testard [:RT]]

Marking this bug as closed as the issue did not re-appear in the last few updates.

Comment 8

[Mark Banner (:standard8)]

FYI, we use WORKSFORME if we don't know what fixed it (or if it can't be reproduced).