985412 - Multiple instances of "A promise chain failed to handle a rejection at resource://gre/modules/FrameWorker.jsm:161" in browser_social_workercrash.js

Status: RESOLVED FIXED

(Firefox Graveyard :: SocialAPI, defect)

Description

[David Teller [:Yoric] - still alive but not very active]

Once we land bug 976205, the following error will cause oranges.

 WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/social/browser_social_workercrash.js | A promise chain failed to handle a rejection at resource://gre/modules/FrameWorker.jsm:161 - [object Object]
04:16:59     INFO -  Stack trace:
04:16:59     INFO -      JS frame :: resource://gre/modules/FrameWorker.jsm :: ParentPort.prototype._dopost/< :: line 161
04:16:59     INFO -  JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: Handler.prototype.process :: line 809
04:16:59     INFO -  JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.walkerLoop :: line 688
04:16:59     INFO -  native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0

Also, it would be nice if the error had a toString() method.

For testing, you may wish to import the patch of bug 976205.

Comment 1

[David Teller [:Yoric] - still alive but not very active]

If I understand this test correctly, it simulates errors that we would otherwise want to report.
For this test, I'll deactivate mochitest failures for uncaught async errors.

Comment 2

[David Teller [:Yoric] - still alive but not very active]

Attachment: Opting out of async failures

Comment 3

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/integration/fx-team/rev/85ef45466925

Comment 4

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/85ef45466925

Comment 5

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-aurora/rev/7828dcba0865