Closed Bug 1792516 Opened 2 years ago Closed 2 years ago

High frequency dom/ipc/tests/browser_content_shutdown_with_endless_js.js | single tracking bug

Categories

(Core :: DOM: Content Processes, defect, P5)

defect

Tracking

()

RESOLVED FIXED
109 Branch
Tracking Status
firefox109 --- fixed

People

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

References

Details

(Keywords: intermittent-failure, intermittent-testcase)

Attachments

(1 file)

Filed by: abutkovits [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=391544077&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Nga2ulzqTDuo3CGnK75reQ/runs/0/artifacts/public/logs/live_backing.log


[task 2022-09-27T06:23:36.459Z] 06:23:36     INFO - TEST-PASS | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | Shutdown of content process. - 
[task 2022-09-27T06:23:36.460Z] 06:23:36     INFO - Create and shutdown a content process for http://mochi.test:8888/browser/dom/ipc/tests/file_endless_js.html
[task 2022-09-27T06:23:36.460Z] 06:23:36     INFO - Buffered messages finished
[task 2022-09-27T06:23:36.461Z] 06:23:36     INFO - TEST-UNEXPECTED-FAIL | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | Test timed out - 
[task 2022-09-27T06:23:41.455Z] 06:23:41     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-09-27T06:23:41.456Z] 06:23:41     INFO - TEST-UNEXPECTED-FAIL | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | waiting for vsync to be disabled - timed out after 50 tries. - false == true - JS frame :: chrome://mochikit/content/browser-test.js :: ensureVsyncDisabled :: line 592
[task 2022-09-27T06:23:41.456Z] 06:23:41     INFO - Stack trace:
[task 2022-09-27T06:23:41.457Z] 06:23:41     INFO - chrome://mochikit/content/browser-test.js:ensureVsyncDisabled:592
[task 2022-09-27T06:23:41.457Z] 06:23:41     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-09-27T06:23:41.458Z] 06:23:41     INFO - TEST-UNEXPECTED-FAIL | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | vsync remained enabled at the end of the test. Is there an animation still running? Consider talking to the performance team for tips to solve this. - false == true - JS frame :: chrome://mochikit/content/browser-test.js :: ensureVsyncDisabled :: line 593
[task 2022-09-27T06:23:41.458Z] 06:23:41     INFO - Stack trace:
[task 2022-09-27T06:23:41.458Z] 06:23:41     INFO - chrome://mochikit/content/browser-test.js:ensureVsyncDisabled:593
[task 2022-09-27T06:23:41.466Z] 06:23:41     INFO - GECKO(9108) | MEMORY STAT | vsize 2104123MB | vsizeMaxContiguous 65677247MB | residentFast 220MB | heapAllocated 82MB
[task 2022-09-27T06:23:41.467Z] 06:23:41     INFO - TEST-OK | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | took 50091ms
[task 2022-09-27T06:23:41.467Z] 06:23:41     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-09-27T06:23:41.469Z] 06:23:41     INFO - TEST-UNEXPECTED-FAIL | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | Found a tab after previous test timed out: http://mochi.test:8888/browser/dom/ipc/tests/file_endless_js.html - 
[task 2022-09-27T06:23:41.475Z] 06:23:41     INFO - GECKO(9108) | JavaScript warning: http://mochi.test:8888/browser/dom/ipc/tests/file_endless_js.html, line 9: Script terminated by timeout at:
[task 2022-09-27T06:23:41.476Z] 06:23:41     INFO - GECKO(9108) | hang@http://mochi.test:8888/browser/dom/ipc/tests/file_endless_js.html:9:12
[task 2022-09-27T06:23:41.485Z] 06:23:41     INFO - checking window state
[task 2022-09-27T06:23:41.496Z] 06:23:41     INFO - TEST-START | dom/ipc/tests/browser_crash_oopiframe.js
[task 2022-09-27T06:23:41.514Z] 06:23:41     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-09-27T06:23:41.524Z] 06:23:41     INFO - Buffered messages logged at 06:23:41
[task 2022-09-27T06:23:41.524Z] 06:23:41     INFO - Entering test bound test_crashframe
[task 2022-09-27T06:23:41.525Z] 06:23:41     INFO - TEST-PASS | dom/ipc/tests/browser_crash_oopiframe.js | This test only makes sense of we can use OOP iframes. - 
[task 2022-09-27T06:23:41.526Z] 06:23:41     INFO - Console message: [JavaScript Warning: "Script terminated by timeout at:
[task 2022-09-27T06:23:41.526Z] 06:23:41     INFO - hang@http://mochi.test:8888/browser/dom/ipc/tests/file_endless_js.html:9:12
[task 2022-09-27T06:23:41.526Z] 06:23:41     INFO - " {file: "http://mochi.test:8888/browser/dom/ipc/tests/file_endless_js.html" line: 9}]
[task 2022-09-27T06:23:41.527Z] 06:23:41     INFO - Buffered messages finished
[task 2022-09-27T06:23:41.528Z] 06:23:41     INFO - TEST-UNEXPECTED-FAIL | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | Uncaught exception received from previously timed out test - at chrome://mochitests/content/browser/dom/ipc/tests/browser_content_shutdown_with_endless_js.js:31 - TypeError: can't access property "frameLoader", otherBrowser is null
[task 2022-09-27T06:23:41.528Z] 06:23:41     INFO - Stack trace:
[task 2022-09-27T06:23:41.528Z] 06:23:41     INFO - createAndShutdownContentProcess/<@chrome://mochitests/content/browser/dom/ipc/tests/browser_content_shutdown_with_endless_js.js:31:23
[task 2022-09-27T06:23:41.528Z] 06:23:41     INFO - withNewTab@resource://testing-common/BrowserTestUtils.jsm:151:24
[task 2022-09-27T06:23:41.529Z] 06:23:41     INFO - GECKO(9108) | JavaScript error: chrome://mochikit/content/browser-test.js, line 1108: TypeError: can't access property "shift", currentScope.__tasks is null
[task 2022-09-27T06:23:41.529Z] 06:23:41     INFO - Console message: [JavaScript Error: "TypeError: can't access property "shift", currentScope.__tasks is null" {file: "chrome://mochikit/content/browser-test.js" line: 1108}]
[task 2022-09-27T06:23:41.557Z] 06:23:41     INFO - Console message: [JavaScript Warning: "Partitioned cookie or storage access was provided to http://example.com/ because it is loaded in the third-party context and dynamic state partitioning is enabled."]
[task 2022-09-27T06:23:41.568Z] 06:23:41     INFO - Console message: [JavaScript Warning: "This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use <!DOCTYPE html>." {file: "http://example.com/" line: 0}]
[task 2022-09-27T06:23:41.580Z] 06:23:41     INFO - TEST-PASS | dom/ipc/tests/browser_crash_oopiframe.js | oop frame has root as parent 

Lately, this is failing frequent with this failure line TEST-UNEXPECTED-FAIL | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | Test timed out -

Hi Artur! Can you please take a look at this?
Thank you!

Flags: needinfo?(aiunusov)
Summary: Intermittent dom/ipc/tests/browser_content_shutdown_with_endless_js.js | single tracking bug → Frequent dom/ipc/tests/browser_content_shutdown_with_endless_js.js | single tracking bug
Summary: Frequent dom/ipc/tests/browser_content_shutdown_with_endless_js.js | single tracking bug → High frequency dom/ipc/tests/browser_content_shutdown_with_endless_js.js | single tracking bug

Looking at

[task 2022-12-03T12:34:04.905Z] 12:34:04     INFO - Buffered messages logged at 12:33:20
[task 2022-12-03T12:34:04.905Z] 12:34:04     INFO - TEST-PASS | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | Content process created. - 
[task 2022-12-03T12:34:04.905Z] 12:34:04     INFO - TEST-PASS | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | Shutdown of content process. - 
[task 2022-12-03T12:34:04.905Z] 12:34:04     INFO - Create and shutdown a content process for http://mochi.test:8888/browser/dom/ipc/tests/file_endless_js.html
[task 2022-12-03T12:34:04.905Z] 12:34:04     INFO - Buffered messages finished

suggests, that this is basically the same as we had in bug 1782718, that is we do never get the notification that the tab has loaded. I wonder if we should try to add a real timeout >0 here at <body onload="setTimeout(hang)"> ?

Flags: needinfo?(aiunusov) → needinfo?(smaug)

Or send an explicit message to the page to trigger the hang?

I wonder if one can reproduce this locally on an opt build, when running with --verify or something.

Flags: needinfo?(smaug)
Assignee: nobody → jstutte
Status: NEW → ASSIGNED
Pushed by jstutte@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5b38548871de Have an explicit message to start the hang function. r=smaug
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 109 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: