1697867 - Google Meet consumes a lot of CPU on Mac

Status: RESOLVED DUPLICATE of bug 1670193

(Core :: WebRTC, defect, P2)

Description

[Eric Rescorla (:ekr)]

Katherine Bose reports that Meet consumes a lot of CPU on mac. Can someone please investigate?

Comment 1

[Nils Ohlmeier [:drno]]

I was in a Meet meeting today with 6 participants and it consumed about 20% CPU on my 2018 MBP, which I would consider fairly reasonable.

But we are planing on reaching out to the performance team to get help investigating what parts of our code could be optimize.

Comment 2

[Patricia Lawless]

Setting this to P1 for investigation and analysis so we can determine its true impact to the user.

Comment 3

[Michael Froman [:mjf]]

Reverting this to P2 since we're not currently getting feedback on this issue.

Comment 4

[Stanislaw Pitucha]

I'm happy to provide more information as needed.
From experience, the CPU usage bounces between 40+% but stable and 100% and dropping frames, transmitting robot voice.
The things that trigger the 100% usage for me are - using a usb attached mic and switching focus away from the firefox window.

Is there something I can monitor to provide more info and narrow down the problem?
(for comparison, chrome is super-smooth in the same environment, with the same devices)

Comment 5

[Stanislaw Pitucha]

Issues happen for me on darwin 21.3.0 with ff 97.0.1

Comment 6

[Florian Quèze [:florian]]

(In reply to Stanislaw Pitucha from comment #4)

Is there something I can monitor to provide more info and narrow down the problem?

You can look at about:processes to see which process is using the CPU. You can also see which threads if you use a Nightly, or set toolkit.aboutProcesses.showThreads to true from about:config.

Capturing and sharing here a profile with the Firefox Profiler (https://profiler.firefox.com/) would also help understand what's happening.

Comment 7

[Stanislaw Pitucha]

The attachment upload fails for me for some reason, so here's the screenshot of about:processes during the call: https://imgur.com/a/eDqYufA
This time it was without a usb attached mic - turned out to be a red herring. I didn't get a robot voice, just lots of dropped frames and everything was super slow.

Comment 8

[Stanislaw Pitucha]

I'll try to follow up with the profiler results, but won't be able to do that for at least 2 weeks. If anyone else can do it in the meantime, please do.

Comment 9

[Stanislaw Pitucha]

Another screenshot with the main process threads visible: https://imgur.com/a/fhgejAo

Comment 10

[Florian Quèze [:florian]]

(In reply to Stanislaw Pitucha from comment #8)

Thanks for the about:processes screenshots!

I'll try to follow up with the profiler results, but won't be able to do that for at least 2 weeks. If anyone else can do it in the meantime, please do.

If you already have the issue visible in about:processes, capturing a profile is a single click (if you are on Nightly; if not you will need to set toolkit.aboutProcesses.showProfilerIcons to true from about:config). There's a profiler icon appearing when you hover the process name ("https://google.com/ (1343)" in your screenshot). Click it, and 5s later a profiler tab will open, from which you can easily upload the profile.