1720511 - Typing responses in Google Mail stopped working when sharing a process with a meeting in Meet

Status: NEW

(Core :: DOM: Content Processes, defect, P3)

Description

[alex_mayorga]

¡Hola y'all!

Typing replies on https://mail.google.com/mail/u/0/#inbox stopped working altogether and the CPU was at 100%

I captured a profile at https://share.firefox.dev/3wHLEYt

Please let me know if anything further is needed from the profile or device.

¡Gracias!
Alex

Comment 1

[Adrian Florinescu [:aflorinescu]]

Mike, can you pretty please take a look at the reported profile?

Comment 2

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

Hi! No need to say "pretty" please, of course I'll do it. :p

What's going on here is that a Google Meet session was also running, and in the same process. The Google Meet application was consuming the vast majority of the content process main thread CPU cycles for doing things like:

1. Painting
2. Reacting to audioprocess events
3. Running requestAnimationFrame callback functions
4. Garbage collecting
5. Updating the IntersectionObservers code

So there's a lot going on here. One thing to consider is that maybe heavy applications like Meet should probably get their own content process.

alex_mayorga, when you captured this profile, was the Google Meet tab or window in the foreground and visible?

Comment 3

[alex_mayorga]

¡Hola Mike!

Hope these lines find you well.

There's indeed a window with a https://meet.google.com/ always visible on the setup for collaboration with my colleagues in "the office".

Hope this is helpful.

¡Gracias!
Alex

Comment 4

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

Hey jesup, this looks like a case with Fission where we've got multiple heavy applications from the same domain running in the same content process. Pre-Fission, the pages would have been distributed more randomly across content processes, so this probably would have been harder to hit. Anything to do here? Perhaps we have some plans for more clever load distribution?

Comment 5

[Randell Jesup [:jesup] (needinfo me)]

We are experimenting with not putting all tabs from the same domain in the same process, for that and several other reasons. It's far easier to switch on something like excessive memory use (or perhaps GC/CC times) than CPU, which tends to be transitory and hard to measure accurately, but partitioning on CPU time is possible.

Comment 6

[alex_mayorga]

¡Hola y'all!

Hope these lines find y'all well.

I had another case of choppy https://meet.google.com/ today and captured this profile:

https://share.firefox.dev/3zvYlrz

It is pretty much unusable and I can't in good faith suggest my colleagues to use Firefox for meetings in "El Goog" anymore.

Is this the same bug or a separate one?

I also believe this should be higher than a P3 given the prevalence of this meeting solution nowadays.

¡Gracias!
Alex

Comment 7

[Olli Pettay [:smaug][[e-mail]](vacation until July 14)]

Parent process is very quiet (98% idle), an the relevant child process isn't too active either (68% idle) in the profile from comment 6.
GPU Process' renderer is a bit busier than usually, but I guess if there is a video playing back, that is expected.

Alex, do you have something else running in your system affecting the behavior? That profile looks rather good.

Comment 8

[Jeff Muizelaar [:jrmuizel]]

Alex, also, if you do get a new profile can you turn off screenshots or use the Graphics preset?

Comment 9

[Randell Jesup [:jesup] (needinfo me)]

Note also that we landed multiple processes per site a couple of months ago, specifically to help with responsiveness in cases where you have a bunch of tabs open from e.g. google which are 'heavy' (meet, docs, calendar, etc). Exactly which tabs ends up sharing will be luck of the draw currently.

Comment 10

[alex_mayorga]

¡Hola y'all!

¡Feliz 2022!

Apologies for the late response here.

Please find another profile of meet.google.com making the laptop fans spin like crazy:

https://share.firefox.dev/3KGhrRO

This was with just me staring an instant meeting.

Happy to hop into a Google Meeting with y'all if that makes more sense.

¡Gracias!
Alex

Comment 11

[Olli Pettay [:smaug][[e-mail]](vacation until July 14)]

That doesn't really show much happening in Firefox.
Did you see high cpu usage in OS' system monitor?

Comment 12

[Frank Doty [:fdoty]]

The Performance Priority Calculator has determined this bug's performance priority to be P2.

Impact on site: Renders site effectively unusable (+3)
Affects macOS or Windows: One of them (×3)
Configuration: Rare (×0.3)
[x] Causes severe resource usage (+2)
[x] Affects major website (×5)

Comment 13

[Olli Pettay [:smaug][[e-mail]](vacation until July 14)]

Alex, have you seen this recently? I do use Google meet every now and then and while doing that also use Google doc etc. and haven't seen anything like this. And I just re-tested this and ensured Gmail and Meet run in the same process and based on profiles, processes were mostly idle.
When typing in GMail, the process is a bit busy, since it triggers so much network traffic, but the process was still mostly idle.