1603925 - Intermittent dom/tests/browser/browser_ConsoleStorageAPITests.js | Uncaught exception - [Exception... "(null)" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "<unknown>" data: no]

Status: RESOLVED FIXED

(DevTools :: General, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: aciure [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=281174434&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/FkYm63nWS7GM1jCm5-Q06Q/runs/0/artifacts/public/logs/live_backing.log

---

[task 2019-12-14T10:08:57.188Z] 10:08:57 INFO - TEST-PASS | dom/tests/browser/browser_ConsoleStorageAPITests.js | Cleared Storage - 0 == 0 -
[task 2019-12-14T10:08:57.188Z] 10:08:57 INFO - Buffered messages finished
[task 2019-12-14T10:08:57.188Z] 10:08:57 INFO - TEST-UNEXPECTED-FAIL | dom/tests/browser/browser_ConsoleStorageAPITests.js | Uncaught exception - [Exception... "(null)" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "<unknown>" data: no]
[task 2019-12-14T10:08:57.188Z] 10:08:57 INFO - Leaving test bound
[task 2019-12-14T10:08:57.188Z] 10:08:57 INFO - GECKO(2959) | MEMORY STAT | vsize 20974928MB | residentFast 1060MB
[task 2019-12-14T10:08:57.188Z] 10:08:57 INFO - TEST-OK | dom/tests/browser/browser_ConsoleStorageAPITests.js | took 2039ms
[task 2019-12-14T10:08:57.188Z] 10:08:57 INFO - checking window state

Comment 1

[Intermittent Failures Robot]

7 failures in 4867 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 3
• try: 3
• mozilla-central: 1

Platform breakdown:

• linux64: 6
• windows10-64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1603925&startday=2019-12-09&endday=2019-12-15&tree=all

Comment 2

[Cristina Coroiu [:ccoroiu]]

Retriggers: https://treeherder.mozilla.org/#/jobs?repo=autoland&searchStr=Linux%2Cx64%2Casan%2CMochitests%2Ctest-linux64-asan%2Fopt-mochitest-browser-chrome-e10s-6%2CM%28bc6%29&tochange=9ffd4ecbfc2b3b9255e66588111a0af2140d0559&fromchange=59ecd0b2823006cee80869b744407bfec7de8cd3&selectedJob=281877417

Kris, please take a look.

Comment 3

[Intermittent Failures Robot]

39 failures in 4582 pushes (0.009 failures/push) were associated with this bug in the last 7 days.

This is the #37 most frequent failure this week.

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **

Repository breakdown:

• autoland: 22
• try: 15
• mozilla-central: 2

Platform breakdown:

• linux64: 34
• windows10-64: 5

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1603925&startday=2019-12-16&endday=2019-12-22&tree=all

Comment 4

[Intermittent Failures Robot]

27 failures in 1365 pushes (0.02 failures/push) were associated with this bug in the last 7 days.

This is the #32 most frequent failure this week.

Repository breakdown:

• try: 9
• mozilla-central: 8
• autoland: 10

Platform breakdown:

• linux64: 19
• windows10-64: 8

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1603925&startday=2019-12-23&endday=2019-12-29&tree=all

Comment 5

[Alexandru Michis [:malexandru]]

Julian,
This has quite a high failure rate on the beta simulations and on integration as well:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=db5256ada418a2770ae296caf42b1e89b2f15f56&searchStr=linux%2Cx64%2Casan%2Cmochitests%2Ctest-linux64-asan%2Fopt-mochitest-browser-chrome-e10s-14%2Cm%28bc14%29&selectedJob=283347245

Could you please look into it?

Comment 6

[Julian Descottes [:jdescottes]]

Seems like there are two calls to BrowserTestUtils.addTab without await right before we call SpecialPowers.spawn. So we might try to use JSWindowActors that will be destroyed by navigation?

Let's see if that fixes it:

• push on top of the beta simulation https://treeherder.mozilla.org/#/jobs?repo=try&revision=174bba183b4e4a9af5e7a8b6acf7abf75574771a
• beta simulation baseline https://treeherder.mozilla.org/#/jobs?repo=try&revision=644881e7b442bf38f3caa5d704daaee8838df65f
• push on top of central https://treeherder.mozilla.org/#/jobs?repo=try&revision=56b421d3fb09d85b81e7524e595b017a8638c8eb

Comment 7

[Intermittent Failures Robot]

35 failures in 1862 pushes (0.019 failures/push) were associated with this bug in the last 7 days.

This is the #14 most frequent failure this week.

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **

Repository breakdown:

• autoland: 17
• mozilla-central: 2
• try: 16

Platform breakdown:

• linux64: 25
• windows10-64: 10

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1603925&startday=2019-12-30&endday=2020-01-05&tree=all

Comment 8

[Julian Descottes [:jdescottes]]

Adding await before those addTab calls didn't work, but it seems the issue is with

  await SpecialPowers.spawn(browser, [], function() {
    // make sure a closed window's events are in fact removed from
    // the storage cache
    content.console.log("adding a new event");
  });

Right before, the test tab navigates from about:blank to a test document, and even though we wait for DOMContentLoaded, it seems this is called too soon and we get old JSWindowActors instead of the ones for the new global?

I can try to workaround this, but I'm confused as to why the approach here is invalid.

Comment 9

[Julian Descottes [:jdescottes]]

Attachment: Bug 1603925 - Wait for navigation in browser_ConsoleStorageAPITests.js

Additionally waiting for a DOM element fixes the intermittent, but this is a workaround.

Comment 10

[Julian Descottes [:jdescottes]]

I am pushing a patch for working around the issue but it would be great if someone more familiar with JS Window Actors could check if the pattern used in the test (waiting for DOMContentLoaded) is bad (what should be done instead?) or if something needs to be looked at on the platform side.

Hopefully, kmag can share some advice.

Comment 11

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/230e7d093c19
Wait for navigation in browser_ConsoleStorageAPITests.js r=nchevobbe

Comment 12

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-beta/rev/11052e729f94

Comment 13

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/230e7d093c19

Comment 14

[Intermittent Failures Robot]

6 failures in 4472 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 1
• autoland: 3
• try: 1
• mozilla-beta: 1

Platform breakdown:

• linux64: 4
• windows10-64: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1603925&startday=2020-01-06&endday=2020-01-12&tree=all

Comment 15

[Intermittent Failures Robot]

2 failures in 4004 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• try: 1
• mozilla-beta: 1

Platform breakdown:

• linux64: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1603925&startday=2020-01-20&endday=2020-01-26&tree=all