Closed Bug 1559484 Opened 5 years ago Closed 4 years ago

Add a test for reloading a document with OOP iframe

Categories

(Core :: DOM: Content Processes, task, P2)

task

Tracking

()

RESOLVED WONTFIX
Fission Milestone Future
Tracking Status
firefox76 --- affected

People

(Reporter: nika, Assigned: farre)

References

(Blocks 1 open bug)

Details

Attachments

(1 obsolete file)

This appears to happen in https://searchfox.org/mozilla-central/rev/d62176d3d70bbf9ad86a5d444f9edada52cbc2b1/docshell/base/BrowsingContextGroup.cpp#76. My guess is that the changes made in bug 1555287 cause there to be a state where not every BrowsingContext is visited by only walking cached & toplevel BCs (as they've been detached as children), so this assert fails.

Andreas, is there any chance you could look into this?

Flags: needinfo?(afarre)
Assignee: nobody → afarre

Bug 1555287 has been backed out so let's keep an eye if the signature disappears.

Flags: needinfo?(afarre)

I can confirm that with Bug 1555287 Comment 14 this hits the assert, and with out that patch it doesn't.

Attachment #9074468 - Attachment description: Bug 1559484 - Test that you can reload a fission iframe. r=nika → Bug 1559484 - Test that you can reload a cross domain iframe.

The patch is ready but we really need it only once we start enabling WPT-fission, so pushing this out to M5 to focus on M-fis for M4.

Fission Milestone: M4 → M5
Blocks: fission
Status: NEW → ASSIGNED
Type: defect → task
Summary: Reloading a document with OOP iframes crashes → Add a test for reloading a document with OOP iframe

Deferring to Fission Nightly (M6) because adding new tests doesn't strictly block Fission dogfooding (M5).

Blocks: WPT-Fis
No longer blocks: fission
Fission Milestone: M5 → M6

The DOM Fission team is relying on feature teams to debug and fix Fission failures in their tests. If the failure looks like a bug in Fission's DOM or IPC changes, you can send the bug back to me.

We're hoping to enable Fission for a subset of Nightly users in early Q3, so we would like WPT tests to be green for Fission by end of Q2. Whether a particular test failure actually blocks shipping Fission is up to the discretion of the feature team. You all would know better than the DOM Fission which test failures are most important.

You can enable Fission when running WPT tests locally using mach wpt --enable-fission.

Nika declares WPT-Fis test bugs should be tracked for Fission M6b.

Fission Milestone: M6 → M6b
Fission Milestone: M6b → Future
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Attachment #9074468 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: