Closed Bug 1601368 Opened 4 years ago Closed 4 years ago

Intermittent dom/ipc/tests/browser_crash_oopiframe.js | The iframe is now pointing at about:framecrashed -

Categories

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

defect

Tracking

()

RESOLVED FIXED
81 Branch
Fission Milestone M6c
Tracking Status
firefox80 --- wontfix
firefox81 --- fixed

People

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

Details

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

Attachments

(1 file)

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


[task 2019-12-04T17:57:41.293Z] 17:57:41 INFO - TEST-START | dom/ipc/tests/browser_crash_oopiframe.js
[task 2019-12-04T17:57:43.959Z] 17:57:43 INFO - TEST-PASS | dom/ipc/tests/browser_crash_oopiframe.js | top frame browsing context id not expected. -
[task 2019-12-04T17:57:43.959Z] 17:57:43 INFO - TEST-PASS | dom/ipc/tests/browser_crash_oopiframe.js | oop frame browsing context id expected. -
[task 2019-12-04T17:57:43.959Z] 17:57:43 INFO - Buffered messages finished
[task 2019-12-04T17:57:43.959Z] 17:57:43 INFO - TEST-UNEXPECTED-FAIL | dom/ipc/tests/browser_crash_oopiframe.js | The iframe is now pointing at about:framecrashed -
[task 2019-12-04T17:57:43.959Z] 17:57:43 INFO - Stack trace:
[task 2019-12-04T17:57:43.959Z] 17:57:43 INFO - chrome://mochikit/content/browser-test.js:test_ok:1299
[task 2019-12-04T17:57:43.960Z] 17:57:43 INFO - chrome://mochitests/content/browser/dom/ipc/tests/browser_crash_oopiframe.js:null:79
[task 2019-12-04T17:57:43.960Z] 17:57:43 INFO - resource://testing-common/BrowserTestUtils.jsm:withNewTab:152
[task 2019-12-04T17:57:43.960Z] 17:57:43 INFO - chrome://mochitests/content/browser/dom/ipc/tests/browser_crash_oopiframe.js:null:18
[task 2019-12-04T17:57:43.960Z] 17:57:43 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1069
[task 2019-12-04T17:57:43.960Z] 17:57:43 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1104
[task 2019-12-04T17:57:43.960Z] 17:57:43 INFO - chrome://mochikit/content/browser-test.js:nextTest/<:932
[task 2019-12-04T17:57:43.960Z] 17:57:43 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:805
[task 2019-12-04T17:57:43.960Z] 17:57:43 INFO - GECKO(4811) | [Child 5188: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 6 (0x7f3b994d4400) [pid = 5188] [serial = 7] [outer = 0x7f3b996b3100]
[task 2019-12-04T17:57:43.961Z] 17:57:43 INFO - Leaving test bound
[task 2019-12-04T17:57:43.961Z] 17:57:43 INFO - GECKO(4811) | [Child 5188: Main Thread]: I/DocShellAndDOMWindowLeak --DOCSHELL 0x7f3b983c3000 == 2 [pid = 5188] [id = {5bef41a6-64df-4d7b-af3c-9592aba8a68f}] [url = ]
[task 2019-12-04T17:57:43.961Z] 17:57:43 INFO - GECKO(4811) | MEMORY STAT | vsize 2965MB | residentFast 350MB | heapAllocated 108MB
[task 2019-12-04T17:57:43.961Z] 17:57:43 INFO - TEST-OK | dom/ipc/tests/browser_crash_oopiframe.js | took 1748ms
[task 2019-12-04T17:57:43.961Z] 17:57:43 INFO - checking window state

This intermittent test failure doesn't need to block Fission MVP unless it becomes more frequent.

Fission Milestone: --- → Future
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---

This Fission test used to intermittently fail about once a week, then it stopped failing for four months, and now it's failed three times just today?? We should keep an eye on this test.

https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?startday=2020-06-30&endday=2020-07-07&tree=trunk&bug=1601368

This bug failed 33 times in the past 7 days. This happened on linux1804-64 debug.

Recent log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=312358817&repo=autoland&lineNumber=4035

Neha, could you assign someone to look into it?

Flags: needinfo?(nkochar)
Whiteboard: [stockwell needswork:owner]

Kashav, can you look into this, please?

Flags: needinfo?(nkochar) → needinfo?(kmadan)

I wasn't able to reproduce locally in a few verify runs. Fortunately, it appears that it's failing consistently here. It'd be helpful to know what newIframeURI actually is at that point.

Assignee: nobody → kmadan
Status: REOPENED → ASSIGNED
Flags: needinfo?(kmadan)

(In reply to :kashav from comment #21)

It'd be helpful to know what newIframeURI actually is at that point.

It's about:blank. We explicitly wait for a non about:blank WindowGlobalParent, so it looks like WindowGlobalParent.documentURI and Document.documentURI may be getting out-of-sync.

Fission Milestone: Future → M6c
Severity: normal → S3
Priority: P5 → P3

It's possible to end up in a situation where the window global has been set on
the BrowsingContext, but hasn't yet been initialized. Proceeding at this point
results in the document having a stale URI (about:blank in this case). Waiting
for a "window-global-created" instead should ensure that everything has been
initialized before we proceed.

Pushed by kmadan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9ce0ad253b41
Wait for a "window-global-created" instead of polling for a currentWindowGlobal, r=mconley
Status: ASSIGNED → RESOLVED
Closed: 4 years ago4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: