1802769 - Firefox in a mostly unresponsive state, creating new tabs, new window -> new tab works but loading content fails

Status: RESOLVED DUPLICATE of bug 1798780

(Core :: DOM: Navigation, defect)

Description

[Mark]

Attachment: Screenshot from 2022-11-27 11-41-02.png

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:107.0) Gecko/20100101 Firefox/107.0

Steps to reproduce:

In continuation of #1553644 (CLOSED WORKSFORME, not by me), I now find this bug appears in 107.0.

I can reliably reproduce it by using long-press on the back/forward buttons, using very specific steps.

1. Go to https://github.com/double-commander/doublecmd
2. Enter "duplicate files" in the search box and press enter
3. Click on "Commits"
4. Click on the commit named "ADD: Find duplicate files"
5. Click on a file at the left to jump to a bookmark link
   6A. Long-press the back button and click on the oldest one (going 4 steps back), or
   6B. Long-press the back button and instead go only 3 steps back
6. Long-press the forward button and click on the newest

Actual results:

Case 6A: Firefox enters an inconsistent state where the page area remains blank and the browser console is spammed with errors. Three of which seem to be recurring at random:

initialBrowser.frameLoader.remoteTab is null
this.browsingContext is null
Promise object could not be cloned

Base 6B: The URL changes but the page does not. Presumably it tries to find the bookmark (for the clicked source file) on the displayed page (search page) which does not exist. The problem may be deeper than this, causing invisible inconsistent state, but I can't find evidence of this.

Expected results:

Should work the same as going back in discrete steps with the back button (in step 6) and/or then going forward the same amount of steps with the forward button (in step 7).

Comment 1

[Rares Doghi, Desktop QA]

I was able to reproduce this issue on a Windows 10 machine on both ESR 102.5 as well as our Latest Release 107.0.1, but it no longer occurs in our latest Beta or Nightly builds.

Errors I saw in our Browser console:
Uncaught TypeError: initialBrowser.frameLoader.remoteTab is null
AsyncTabSwitcher resource:///modules/AsyncTabSwitcher.jsm:172
_getSwitcher chrome://browser/content/tabbrowser.js:5347
warmupTab chrome://browser/content/tabbrowser.js:5354
_mouseenter chrome://browser/content/tabbrowser-tab.js:542
on_mouseover chrome://browser/content/tabbrowser-tab.js:318
handleEvent chrome://global/content/customElements.js:463

2 AsyncTabSwitcher.jsm:172:1
AsyncTabSwitcher resource:///modules/AsyncTabSwitcher.jsm:172
_getSwitcher chrome://browser/content/tabbrowser.js:5347
warmupTab chrome://browser/content/tabbrowser.js:5354
_mouseenter chrome://browser/content/tabbrowser-tab.js:542
on_mouseover chrome://browser/content/tabbrowser-tab.js:318
handleEvent chrome://global/content/customElements.js:463

TypeError: this.browsingContext is null
2 browser-custom-element.js:399:7
set docShellIsActive chrome://global/content/elements/browser-custom-element.js:399
setTabState resource:///modules/AsyncTabSwitcher.jsm:281
loadRequestedTab resource:///modules/AsyncTabSwitcher.jsm:536
postActions resource:///modules/AsyncTabSwitcher.jsm:641
handleEvent resource:///modules/AsyncTabSwitcher.jsm:1129

Comment 2

[Rares Doghi, Desktop QA]

It seems that it was fixed by Bug 1798780.

Comment 3

[Rares Doghi, Desktop QA]

Marking it as a dupe of Bug 1798780, it seems that its the same exact issue and I was able to verify the fix for it.

Comment 4

[Rares Doghi, Desktop QA]

Verified as fixed in our latest ESR build 102.6 using the scenario from the description.