Closed Bug 1783652 Opened 2 years ago Closed 2 years ago

Intermittent dom/ipc/tests/browser_content_shutdown_with_endless_js.js | single tracking bug

Categories

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

defect

Tracking

()

RESOLVED DUPLICATE of bug 1782718

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, intermittent-testcase)

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


[task 2022-08-08T12:09:42.337Z] 12:09:42     INFO - TEST-PASS | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | Shutdown of content process. - 
[task 2022-08-08T12:09:42.338Z] 12:09:42     INFO - Create and shutdown a content process for http://mochi.test:8888/browser/dom/ipc/tests/file_endless_js.html
[task 2022-08-08T12:09:42.338Z] 12:09:42     INFO - Buffered messages finished
[task 2022-08-08T12:09:42.339Z] 12:09:42     INFO - TEST-UNEXPECTED-FAIL | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | Test timed out - 
[task 2022-08-08T12:09:47.319Z] 12:09:47     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-08-08T12:09:47.321Z] 12:09:47     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 575
[task 2022-08-08T12:09:47.321Z] 12:09:47     INFO - Stack trace:
[task 2022-08-08T12:09:47.321Z] 12:09:47     INFO - chrome://mochikit/content/browser-test.js:ensureVsyncDisabled:575
[task 2022-08-08T12:09:47.322Z] 12:09:47     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-08-08T12:09:47.323Z] 12:09:47     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 576
[task 2022-08-08T12:09:47.323Z] 12:09:47     INFO - Stack trace:
[task 2022-08-08T12:09:47.323Z] 12:09:47     INFO - chrome://mochikit/content/browser-test.js:ensureVsyncDisabled:576
[task 2022-08-08T12:09:47.331Z] 12:09:47     INFO - GECKO(2008) | MEMORY STAT | vsize 2104128MB | vsizeMaxContiguous 67582008MB | residentFast 223MB | heapAllocated 82MB
[task 2022-08-08T12:09:47.332Z] 12:09:47     INFO - TEST-OK | dom/ipc/tests/browser_content_shutdown_with_endless_js.js | took 50095ms
[task 2022-08-08T12:09:47.333Z] 12:09:47     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-08-08T12:09:47.333Z] 12:09:47     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-08-08T12:09:47.350Z] 12:09:47     INFO - checking window state
[task 2022-08-08T12:09:47.356Z] 12:09:47     INFO - TEST-START | dom/ipc/tests/browser_crash_oopiframe.js
[task 2022-08-08T12:09:47.390Z] 12:09:47     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-08-08T12:09:47.393Z] 12:09:47     INFO - Buffered messages logged at 12:09:47
[task 2022-08-08T12:09:47.394Z] 12:09:47     INFO - Entering test bound test_crashframe
[task 2022-08-08T12:09:47.395Z] 12:09:47     INFO - TEST-PASS | dom/ipc/tests/browser_crash_oopiframe.js | This test only makes sense of we can use OOP iframes. - 
[task 2022-08-08T12:09:47.395Z] 12:09:47     INFO - Buffered messages finished
[task 2022-08-08T12:09:47.396Z] 12:09:47     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-08-08T12:09:47.397Z] 12:09:47     INFO - Stack trace:
[task 2022-08-08T12:09:47.397Z] 12:09:47     INFO - createAndShutdownContentProcess/<@chrome://mochitests/content/browser/dom/ipc/tests/browser_content_shutdown_with_endless_js.js:31:23
[task 2022-08-08T12:09:47.397Z] 12:09:47     INFO - withNewTab@resource://testing-common/BrowserTestUtils.jsm:151:24
[task 2022-08-08T12:09:47.397Z] 12:09:47     INFO - GECKO(2008) | JavaScript error: chrome://mochikit/content/browser-test.js, line 1091: TypeError: can't access property "shift", currentScope.__tasks is null
[task 2022-08-08T12:09:47.398Z] 12:09:47     INFO - Console message: [JavaScript Error: "TypeError: can't access property "shift", currentScope.__tasks is null" {file: "chrome://mochikit/content/browser-test.js" line: 1091}]
[task 2022-08-08T12:09:47.410Z] 12:09:47     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-08-08T12:09:47.425Z] 12:09:47     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-08-08T12:09:47.430Z] 12:09:47     INFO - TEST-PASS | dom/ipc/tests/browser_crash_oopiframe.js | oop frame has root as parent 
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.