Intermittent browser_aboutTabCrashed.js | A promise chain failed to handle a rejection: - at resource://gre/modules/TelemetrySession.jsm:1124 - Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIMessageSender.sendAsyncMessage]

RESOLVED FIXED in Firefox 50

Status

()

defect
P3
normal
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: philor, Unassigned)

Tracking

({intermittent-failure})

unspecified
Firefox 52
Points:
---

Firefox Tracking Flags

(firefox50 fixed, firefox51 fixed, firefox52 fixed)

Details

Attachments

(1 attachment)

Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
This has been failing pretty consistently since late March. Any idea what might be going on, Mike?

39 INFO Starting wait on crash-report-status
40 INFO Topic observed!
41 INFO Iterating crash report extra keys
42 INFO TEST-PASS | browser/base/content/test/general/browser_aboutTabCrashed.js | Crash report had the right extra value for URL -
43 INFO TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_aboutTabCrashed.js | A promise chain failed to handle a rejection:  - at resource://gre/modules/TelemetrySession.jsm:1164 - Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIMessageSender.sendAsyncMessage]
Stack trace:
   JS frame :: resource://gre/modules/TelemetrySession.jsm :: gatherMemory :: line 1164
   JS frame :: resource://gre/modules/TelemetrySession.jsm :: Impl.delayedInit/this._delayedInitTask< :: line 1499
   JS frame :: resource://gre/modules/Task.jsm :: TaskImpl_run :: line 319
   JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: Handler.prototype.process :: line 937
   JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: this.PromiseWalker.walkerLoop :: line 816
   Tester_execTest@chrome://mochikit/content/browser-test.js:784:9
   Tester.prototype.nextTest</<@chrome://mochikit/content/browser-test.js:704:7
   SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:743:59
Flags: needinfo?(mconley)
I think this is a case of TelemetrySession not being prepared to handle the crashed content process case.

Patch coming up.
Flags: needinfo?(mconley)
Comment on attachment 8799929 [details]
Bug 1260316 - Make TelemetrySession more resilient if content processes have crashed.

https://reviewboard.mozilla.org/r/84994/#review83544

I did not know that sendAsyncMessage could throw. *packs that knowledge away for later*

LGTM.
Attachment #8799929 - Flags: review?(chutten) → review+
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6d67a819cff0
Make TelemetrySession more resilient if content processes have crashed. r=chutten
https://hg.mozilla.org/mozilla-central/rev/6d67a819cff0
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 52
Whiteboard: [checkin-needed-aurora][checkin-needed-beta]
https://hg.mozilla.org/releases/mozilla-aurora/rev/ae9a8e3d614c
Whiteboard: [checkin-needed-aurora][checkin-needed-beta] → [checkin-needed-beta]
You need to log in before you can comment on or make changes to this bug.