1711037 - Twitter in a container freezes computer and drags Firefox to a halt

Status: UNCONFIRMED

(Core :: Performance, defect, P3)

Description

[varsites]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0

Steps to reproduce:

Create a container for a Twitter. Log in. Go to the search section to search for people.

Actual results:

Entire computer freezes for a few moments. Mouse unmoveable. RAM usage crawling higher and higher. Only solution is to close at the container tab at which point everything returns to normal.

Expected results:

It should've worked.

I ran the Profiler when doing the above which may provide a clue as to what's happening. Here's the link:
https://share.firefox.dev/3fcVIC5

Comment 1

[Daniel Bodea [:danibodea]]

I have attempted reproducing this bug with the steps in comment 0, but everything worked as expected on my Windows 10 with Firefox Release v88.0.1.

Mike, do you see anything suspicious in this performance profile? Can you help me reproduce it and/or determine a correct component for it?

Comment 2

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

This is pretty bizarre. I can see what the user is reporting - there are large ranges of time where we're missing samples, presumably because the sampling threads aren't getting serviced. From the description in comment 0, it sounds like the main thread in the parent process might not be getting serviced either.

varsites, do you have any third-party security software running on your machine?

Comment 3

[varsites]

Just the Windows Defender built into Windows 10.

Comment 4

[Sean Feng [:sefeng]]

Looks like the OS is suspending the browser. I don't think this is actionable.

Comment 5

[Toshihito Kikuchi [:toshi]]

varsites, are you still having this issue?

(In reply to Sean Feng [:sefeng] from comment #4)

Looks like the OS is suspending the browser. I don't think this is actionable.

I think the description "Entire computer freezes for a few moments. Mouse unmoveable. RAM usage crawling higher and higher. Only solution is to close at the container tab at which point everything returns to normal." does not match OS was suspending the browser.

Comment 6

[varsites]

Yes, though not as drastically. The browser still slows drastically when opening a Twitter tab in a container (like if I'm playing music in another tab, the playback starts glitching) but it's no longer 100% frozen. I just did a second ago and that's what happened - Firefox RAM and CPU shot up with Twitter container. BTW and dunno if this is relevant but Tweetdeck in the same Twitter container behaves totally normally; it's only when going to twitter.com in the container that Firefox starts choking.

Comment 7

[Toshihito Kikuchi [:toshi]]

Thank you for the update. The issues of Firefox Multi-Account Containers are managed in GitHub. You may find more experts there. Can you take a look at https://github.com/mozilla/multi-account-containers/issues? It seems that there are several opened performance issues like this.

Comment 8

[Toshihito Kikuchi [:toshi]]

Moving back to the original component as this issue is not related to third-party software.

Comment 9

[Andrew Creskey [:acreskey]]

If anyone else can reproduce this, please share details.