1646894 - Figure out why browser_replace_load.js fails with DocumentChannel process switching

Status: NEW

(Firefox :: Session Restore, defect)

Description

[Matt Woodrow (:mattwoodrow)]

Bug 1646892 is making process switches from content->parent happen via DocumentChannel, which appears to break browser_replace_load.js

I believe the issue is here - https://searchfox.org/mozilla-central/rev/5e6c7717255ca9638b2856c2b2058919aec1d21d/browser/base/content/browser.js#8364

The loadURI call no longer triggers a process switch in firefox, but instead just sends the uri to the content process (and we'll trigger a process switch mid-load).

The following set index call activates the browser, which notifies SessionStore, which calls updateBrowserRemotenessByURL, forcing a new process switch and clobbering the in-progress load.

We might need to make sure we have a way of avoiding this race.

Gijs and I couldn't find a way that this issue would be triggered outside of tests, so I'm hoping to disable the test for now since it'll otherwise block fission.

Comment 1

[BugBot [:suhaib / :marco]]

The severity field is not set for this bug.
:mikedeboer, could you have a look please?

For more information, please visit auto_nag documentation.