1106400 - When opening a Hello window, an error is generated: "A promise chain failed to handle a rejection."

Status: RESOLVED WORKSFORME

(Hello (Loop) :: Client, defect)

Description

[Yaron]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:34.0) Gecko/20100101 Firefox/34.0
Build ID: 20141126041045

Steps to reproduce:

On opening a new window:

A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'?
See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise

Comment 1

[:Gijs (he/him)]

This bug isn't actionable - that error message is generic. We need the location of *where* a promise failed to catch a rejection. There should be a link to a file and a line number. You've also not said what version of Firefox you're seeing this on - please let us know!

Comment 2

[Yaron]

When I reported the bug, that error appeared in the Error Console on opening a new window.

FF 34. No link to a file.

Later, the setting "loop.throttled" (false) was added to pref.js and the error does not appear any more.
Remove or reset "loop.throttled", and you'll see it.

Regards.

Comment 3

[:Gijs (he/him)]

(In reply to Yaron from comment #2)
> When I reported the bug, that error appeared in the Error Console on opening
> a new window.
> 
> FF 34. No link to a file.
> 
> Later, the setting "loop.throttled" (false) was added to pref.js and the
> error does not appear any more.
> Remove or reset "loop.throttled", and you'll see it.
> 
> Regards.

Still not seeing it, although I'm testing on Mac. Also, as soon as I open a new window, the pref gets re-set to false.

Are you seeing this on a clean profile? Are you sure it's not related to an add-on you're using (try in safe mode?).

Comment 4

[Yaron]

Java Console.

In safe-mode after removing "loop.throttled" from pref.js.
http://s7.postimg.org/v8gp01lej/Error_Console.png

"loop.throttled" (false) is now added after closing the browser.
This was not the behavior when I reported the bug.

Comment 5

[Mark Banner (:standard8)]

I've just checked with the latest beta on Windows and we're not getting this error any more. I think this was probably an old error that we had in 34 that we fixed at some stage.

Hence marking as works for me. If this still happens, please re-open with a description of when this happens, or file a new bug.