Closed Bug 1369915 Opened 8 years ago Closed 8 years ago

Intermittent browser_UsageTelemetry_content_aboutHome.js | A promise chain failed to handle a rejection: this._window.document.body is null - rejection date: Fri Jun 02 2017 12:10:39 GMT-0700 (PDT)

Categories

(Firefox :: General, defect, P1)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: intermittent-bug-filer, Assigned: rexboy)

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell disabled][fxsearch])

Attachments

(1 file)

Component: Telemetry → General
Product: Toolkit → Firefox
36 failures since the 18th, this has increased in frequency and we should start looking into this. It seems to fail on a mix of opt/debug, but not in e10s. here is a recent linux64 asan log: https://treeherder.mozilla.org/logviewer.html#?repo=mozilla-central&job_id=109509561&lineNumber=3091 and the related information from the log: [task 2017-06-23T10:02:25.527931Z] 10:02:25 INFO - TEST-PASS | browser/modules/test/browser/browser_UsageTelemetry_content_aboutHome.js | browser.engagement.navigation.about_home must be recorded. - true == true - [task 2017-06-23T10:02:25.530015Z] 10:02:25 INFO - TEST-PASS | browser/modules/test/browser/browser_UsageTelemetry_content_aboutHome.js | browser.engagement.navigation.about_home must contain the 'search_enter' key. - true == true - [task 2017-06-23T10:02:25.532029Z] 10:02:25 INFO - TEST-PASS | browser/modules/test/browser/browser_UsageTelemetry_content_aboutHome.js | 1 - 1 == true - [task 2017-06-23T10:02:25.534117Z] 10:02:25 INFO - TEST-PASS | browser/modules/test/browser/browser_UsageTelemetry_content_aboutHome.js | This search must only increment one entry in the scalar. - 1 == 1 - [task 2017-06-23T10:02:25.536830Z] 10:02:25 INFO - TEST-PASS | browser/modules/test/browser/browser_UsageTelemetry_content_aboutHome.js | The histogram must contain other-MozSearch.abouthome. - true == true - [task 2017-06-23T10:02:25.540077Z] 10:02:25 INFO - TEST-PASS | browser/modules/test/browser/browser_UsageTelemetry_content_aboutHome.js | The key other-MozSearch.abouthome must contain 1. - 1 == 1 - [task 2017-06-23T10:02:25.541835Z] 10:02:25 INFO - Buffered messages finished [task 2017-06-23T10:02:25.545338Z] 10:02:25 INFO - TEST-UNEXPECTED-FAIL | browser/modules/test/browser/browser_UsageTelemetry_content_aboutHome.js | A promise chain failed to handle a rejection: this._window.document.body is null - rejection date: Fri Jun 23 2017 10:02:23 GMT+0000 (UTC) - stack: null - false == true - JS frame :: resource://testing-common/PromiseTestUtils.jsm :: assertNoUncaughtRejections :: line 255 [task 2017-06-23T10:02:25.547153Z] 10:02:25 INFO - Stack trace: [task 2017-06-23T10:02:25.548814Z] 10:02:25 INFO - resource://testing-common/PromiseTestUtils.jsm:assertNoUncaughtRejections:255 [task 2017-06-23T10:02:25.551323Z] 10:02:25 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:801 [task 2017-06-23T10:02:25.553341Z] 10:02:25 INFO - Tester_execTest@chrome://mochikit/content/browser-test.js:774:9 [task 2017-06-23T10:02:25.558654Z] 10:02:25 INFO - Tester.prototype.nextTest</<@chrome://mochikit/content/browser-test.js:686:7 [task 2017-06-23T10:02:25.560524Z] 10:02:25 INFO - SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:795:59 [task 2017-06-23T10:02:25.562993Z] 10:02:25 INFO - Leaving test bound test_abouthome_simpleQuery [task 2017-06-23T10:02:25.564906Z] 10:02:25 INFO - GECKO(1912) | MEMORY STAT | vsize 20973978MB | residentFast 709MB [task 2017-06-23T10:02:25.568766Z] 10:02:25 INFO - TEST-OK | browser/modules/test/browser/browser_UsageTelemetry_content_aboutHome.js | took 3440ms This test case is documented as being in the toolkit::telemetry component: $ ./mach file-info bugzilla-component browser/modules/test/browser/browser_UsageTelemetry_content_aboutHome.js Toolkit :: Telemetry browser/modules/test/browser/browser_UsageTelemetry_content_aboutHome.js if that is wrong, please indicate so and help us annotate this properly.
Component: General → Telemetry
Product: Firefox → Toolkit
Whiteboard: [stockwell needswork]
:gfritzsche, as the triage owner of toolkit::telemetry (and editor of this test a few times), I see that you changed the component of this bug- could you clarify? If this is toolkit::telemetry can you help find someone on the telemetry team to look into this bug as it is failing quite often these days.
Flags: needinfo?(gfritzsche)
This test is for Firefox code that uses Telemetry, it is not testing Telemetry itself. We started the test, but don't own it. I don't know where that annotation is from. :past, do you know who would own this?
Component: Telemetry → General
Flags: needinfo?(gfritzsche) → needinfo?(past)
Product: Toolkit → Firefox
Flags: needinfo?(past)
Priority: -- → P1
Whiteboard: [stockwell needswork] → [stockwell needswork][fxsearch]
thanks or picking this up :past!
I don't have an owner yet, but someone should work on it soon.
Whiteboard: [stockwell needswork][fxsearch] → [stockwell unknown][fxsearch]
seems that we have many more failures in the last week- a higher push rate could help contribute to that- :past, is this in a queue to pick up in the near future?
Flags: needinfo?(past)
Whiteboard: [stockwell unknown][fxsearch] → [stockwell needswork][fxsearch]
Yes, it still is in our P1 list: https://wiki.mozilla.org/Firefox/Search#Releases However, between other priorities and summer PTO it hasn't been picked up yet.
Flags: needinfo?(past)
The current error I see is JavaScript error: resource://onboarding/onboarding.js, line 764: TypeError: doc.head is null I don't think we have onboarding on about:home, so I suspect this comes from browser_UsageTelemetry_content.js that load about:newTab. Looks like onboarding is waiting for the load listener in _loadCSS, then it proceeds. By the time we reach _loadJS the tab may have been closed. :rexboy, may you look into this problem with onboarding?
Flags: needinfo?(rexboy)
Note that the most updated error points to line 868 that is indeed the doc.head usage in _loadJS
We do load onboarding in both about:home and about:newtab. From comment 14, that may because we postponed the loading process to idle time after window.onload, but I need to do some investigating first.
Assignee: nobody → rexboy
Flags: needinfo?(rexboy)
Whiteboard: [stockwell needswork][fxsearch] → [stockwell needswork][fxsearch][photon-onboarding][triage]
Status: NEW → ASSIGNED
Flags: qe-verify-
Whiteboard: [stockwell needswork][fxsearch][photon-onboarding][triage] → [stockwell needswork][fxsearch][photon-onboarding]
Added some logs to inspect, but I can't reproducible on try yet.. still trying.
Seems it's not easy to reproduce for me -- and at the same time the latest orange count has dropped down to nearly just 1%. I'll continue to investigate by running try. But if it can't be reproduced for a while maybe we can just close it.
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1369915&startday=2017-07-28&endday=2017-08-08&tree=all There has been no failures for a week. Let's assume the cause has been resolved somewhere and close it.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
remove whiteboard tag due to its WORKSFORME
Whiteboard: [stockwell needswork][fxsearch][photon-onboarding] → [stockwell needswork][fxsearch]
Whiteboard: [stockwell needswork][fxsearch] → [stockwell unknown][fxsearch]
the fix is that we disabled the non-e10s testing.
Whiteboard: [stockwell unknown][fxsearch] → [stockwell disabled][fxsearch]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: