Closed
Bug 1035098
Opened 10 years ago
Closed 10 years ago
First Loop call after upgrade fails
Categories
(Hello (Loop) :: Client, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: RT, Assigned: standard8)
References
Details
(Keywords: steps-wanted)
Attachments
(3 files)
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.
Reporter | ||
Comment 1•10 years ago
|
||
Reporter | ||
Comment 2•10 years ago
|
||
Reporter | ||
Comment 3•10 years ago
|
||
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.
Assignee | ||
Comment 4•10 years ago
|
||
Taking to remind me to keep an eye out for this. One question, is the link generated before, or after, the nightly upgrade?
Assignee: nobody → standard8
Reporter | ||
Comment 5•10 years ago
|
||
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
Assignee | ||
Comment 6•10 years ago
|
||
(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.
Assignee | ||
Updated•10 years ago
|
Keywords: testcase-wanted
Assignee | ||
Updated•10 years ago
|
Keywords: testcase-wanted → steps-wanted
Reporter | ||
Comment 7•10 years ago
|
||
Marking this bug as closed as the issue did not re-appear in the last few updates.
Status: NEW → UNCONFIRMED
Ever confirmed: false
Reporter | ||
Updated•10 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 8•10 years ago
|
||
FYI, we use WORKSFORME if we don't know what fixed it (or if it can't be reproduced).
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•