Closed Bug 1576418 Opened 4 years ago Closed 4 years ago

Perma fission browser/base/content/test/trackingUI/browser_trackingUI_cryptominers.js | Test timed out -


(Firefox :: Protections UI, defect, P5)




Firefox 70
Fission Milestone M4
Tracking Status
firefox-esr60 --- unaffected
firefox-esr68 --- unaffected
firefox69 --- unaffected
firefox70 --- fixed


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


(Blocks 1 open bug, Regression)


(Keywords: intermittent-failure, regression, Whiteboard: [retriggered])

Filed by: csabou [at]
Parsed log:
Full log:

[task 2019-08-24T11:11:18.121Z] 11:11:18 INFO - TEST-PASS | browser/base/content/test/trackingUI/browser_trackingUI_cryptominers.js | Shows an exception when appropriate -
[task 2019-08-24T11:11:18.121Z] 11:11:18 INFO - Buffered messages finished
[task 2019-08-24T11:11:18.121Z] 11:11:18 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/trackingUI/browser_trackingUI_cryptominers.js | Test timed out -
[task 2019-08-24T11:11:18.121Z] 11:11:18 INFO - GECKO(8248) | JavaScript error: resource://testing-common/PromiseTestUtils.jsm, line 112: uncaught exception: Object
[task 2019-08-24T11:11:18.122Z] 11:11:18 INFO - Console message: [JavaScript Error: "uncaught exception: Object" {file: "resource://testing-common/PromiseTestUtils.jsm" line: 112}]
[task 2019-08-24T11:11:18.122Z] 11:11:18 INFO - GECKO(8248) | MEMORY STAT | vsize 2104126MB | vsizeMaxContiguous 65239989MB | residentFast 247MB | heapAllocated 88MB
[task 2019-08-24T11:11:18.122Z] 11:11:18 INFO - TEST-OK | browser/base/content/test/trackingUI/browser_trackingUI_cryptominers.js | took 45074ms
[task 2019-08-24T11:11:18.122Z] 11:11:18 INFO - Not taking screenshot here: see the one that was previously logged

This started with this merge to central:
and it's from Bug 1575273. Mike, could you please take a look?

Flags: needinfo?(mozilla)
Regressed by: 1575273
Whiteboard: [retriggered]

I am able to recreate this with my code removed as well.

It's timing out connecting to

This can be recreated locally with:

./mach test --enable-fission browser/base/content/test/trackingUI/browser_trackingUI_cryptominers.js --verify

My code would definitely not affect this as it only comes into play when a policy is enabled.

We think this is bug 1559841

Flags: needinfo?(mozilla)
Regressed by: 1559841
No longer regressed by: 1575273
Flags: needinfo?(jwatt)

This was fixed by the backout of the patch from bug 1559841 on Aug 28th.

Assignee: nobody → jwatt
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 70

FWIW this went away after making the changes Nika suggested in bug 1576413.

Retroactively moving fixed bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to an appropriate Fission Milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:


Fission Milestone: --- → M4
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.