1618308 - New tab stuck on a blank page and loading animation

Status: RESOLVED DUPLICATE of bug 1618936

(Core :: DOM: Content Processes, defect)

Description

[mathieu.carpentier]

Attachment: simplescreenrecorder-2020-02-25_19.49.33.mp4

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

Steps to reproduce:

I don't have exact steps to reproduce the problem. It's random because it does not always happen.

Here what I did today when it happened:

• I disconnected from sync
• I refreshed the browser
• I installed a single extension (1Password X)
• No custom settings
• No custom theme.

I browse normally and at some point I click a link that should open in a new tab. It can be a link on a web site or on the firefox home.

Actual results:

A new tab open as expected to load the new page. But the new tab keeps the "new tab" name with the loading animation and no content is loaded.

Expected results:

Page load normally.

Comment 1

[mathieu.carpentier]

Attachment: browser-console.log

the content of the browser console.

Comment 2

[Mike Conley (:mconley) (:⚙️)]

Hm... this can happen if the content process for the tab is failing to launch. I'm tentatively moving this bug there.

Comment 3

[Julien Cristau [:jcristau]]

It sounds like this is a fairly recent regression.

Comment 4

[mathieu.carpentier]

Few other things I noticed when it happens. The tab becomes unusable:

• clicking the home button does nothing.
• cannot refresh the page.
• entering a new URL doesn't work.

In other words this new tab is "broken". The only thing to do is to close the tab.

Comment 5

[mathieu.carpentier]

Is there anything I could do to gather troubleshooting data ?

Comment 6

[Ethan Tseng [:ethan]]

Chris, could you find someone to triage this bug since Neha is on leave?

Comment 7

[Chris Peterson [:cpeterson]]

(In reply to Ethan Tseng [:ethan] from comment #6)

Chris, could you find someone to triage this bug since Neha is on leave?

Sending to Fission triage. Probably related to increase in content process launch failures (bug 1618936).

Comment 8

[Chris Peterson [:cpeterson]]

duping to bug 1618936