1662825 - Poor performance and call terminated during a Google Meet call

Status: RESOLVED WORKSFORME

(Core :: Graphics: WebRender, defect, P2)

Description

[alex_mayorga]

Basic information

Steps to Reproduce:

Join a call in https://meet.google.com/

Expected Results:

Call is usable.

Actual Results:

Call is unusable and ends unexpectedly.

---

More information

Screenshot: N/A

Profile URL: https://share.firefox.dev/32P760O

Basic systems configuration:

OS version: Windows 10 20201

GPU model: Intel HD Graphics 620

Number of cores: 2

Amount of memory (RAM): 24GB

Thanks so much for your help.

Comment 1

[Bas Schouten (:bas.schouten)]

This is the third bug of this type. All on relatively slow Intel HD hardware, I noticed on this profile the CPU also isn't getting much done in any of the content processes. I wonder if WebRender is causing GPU work that is hogging the bus or other CPU resources causing the CPU not to get much work done.

Comment 2

[Jim Mathies [:jimm]]

Hey Alex, would you please post your about:support text? Thanks!

Comment 3

[Jeff Muizelaar [:jrmuizel]]

Alex, do you think this is a regression? Was it better before?

Comment 4

[alex_mayorga]

¡Hola Jeff!

Prior to me filing the bug, I was logging into this meeting with Firefox Nightly with no major issues.

Had to use Microsoft Edge since this bug surfaced so I believe this to be a regression or a change in Google Meet that had a bad effect.

¡Hola Jim!

about:support is at https://bug1666866.bmoattachments.org/attachment.cgi?id=9177629

I will try and see if this works better on today's Nightly.

¡Gracias!
Alex

Comment 5

[Jeff Muizelaar [:jrmuizel]]

Alex, can you try setting gfx.webrender.force-disabled=true and restarting the browser to see if that helps? If it doesn't please reset it back.

Comment 6

[alex_mayorga]

¡Hola Jeff!

I've captured two profiles:

With gfx.webrender.force-disabled=false
https://share.firefox.dev/3n8IpFK

With gfx.webrender.force-disabled=true
https://share.firefox.dev/3jlUCon

Performance seems much worse with gfx.webrender.force-disabled=true so I've reverted it for the time being.

Hope these profiles will help with y'all's investigation.

Please let me know if there's anything else I should try.

¡Gracias!
Alex

Comment 7

[Jim Mathies [:jimm]]

Bas, doesn't look like this is graphics/wr related.

Comment 8

[Sean Feng [:sefeng]]

Alex, does the issue still occur when you have all extensions disabled? One of the content processes was very busy in the original profile, caused by some extensions, so they were likely contending the CPU resource.

The With gfx.webrender.force-disabled=false profile you posted in comment 6 looks much cleaner than the one in the description, was the call still unusable?

Comment 9

[alex_mayorga]

¡Hola Sean!

Are you able to see which of the add-ons are being problematic perhaps, please?

Here's the list of add-ons form about:support:

Name Type Version Enabled ID
Spanish (Mexico) Dictionary dictionary 1.20.1 true @mxspanishdictionary
Amazon.com extension 1.3 true [e-mail]
Bing extension 1.2 true [e-mail]
DuckDuckGo extension 1.1 true [e-mail]
eBay extension 1.2 true [e-mail]
Facebook Container extension 2.1.2 true @contain-facebook
Google extension 1.1 true [e-mail]
LastPass: Free Password Manager extension 4.57.2.5 true [e-mail]
Pioneer-v2 extension 1.0 true [e-mail]
Stylus extension 1.5.13 true {7a7a4a92-a2a0-41d1-9fd7-1e92480d612d}
uBlock Origin extension 1.30.0 true [e-mail]
Wikipedia (en) extension 1.1 true [e-mail]

With gfx.webrender.force-disabled=false the call was mostly usable but there were blips and then the video and audio will race and catch up.

With gfx.webrender.force-disabled=true the whole Firefox window will get a gray overlay and appear hung at times.

The call was ended abruptly a couple times and meet.google.com will display a message about the network disconnecting but no disconnects were evident outside of Firefox.

Hope this helps.

¡Gracias!
Alex

Comment 10

[Sean Feng [:sefeng]]

Hi Alex,

I think LastPass should be one and I don't know if there are other ones.

It's probably easier for you to figure out which extensions are causing the issue. I'd suggest you disable the extensions one by one and see if the Google meet experience gets significantly better after you've disabled certain extensions. Again, I don't see any extension usage in the profiles you've collected in comment 6, so they might not affect your experience anymore.

I also noticed that you seem to be using a virtual desktop? Honestly, I don't know how this will impact performance. Have you tried to use Google meet in a non-virtual desktop environment?

Comment 11

[alex_mayorga]

¡Hola Sean!

I also noticed that you seem to be using a virtual desktop?

This is surprising to me, AFAIK Windows 10 Pro Insider Preview is installed directly on the SSD on this laptop.

How did you discover this?

Is this something I need to disable via Windows or Firefox settings?

¡Gracias!
Alex

Comment 12

[Sean Feng [:sefeng]]

Hi Alex,

I saw a slow nsWindow::GetWorkspaceID -> GetVirtualDesktopManager call in the profile, so I thought it was a virtual desktop. After asking around, I learned that it doesn't necessarily mean a virtual desktop is being used, so probably I was wrong here.

However, GetVirtualDesktopManager is very slow in your profile, which looks abnormal. I have filed bug 1669357 to address it.

Comment 13

[Markus Stange [:mstange]]

I'm going to move this bug to WebRender, even though we've not conclusively determined that this is a graphics problem.

Comment 14

[alex_mayorga]

¡Hola Sean!

I got Google Meet hogging 99% CPU again today.

I managed to capture a new profile at https://share.firefox.dev/37ZWyPH in case it is useful.

Please let me know if this should be a separate bug.

¡Gracias!
Alex

Comment 15

[Sean Feng [:sefeng]]

Thanks for the profile. I can't see a particular reason why the CPU usage was too high though. It just looks like the browser was busy processing a lot of things. I do notice some suspicious things in the profile, like some slow GC, slow styling and slow paints.

So initially we weren't sure if this was related to graphics, however, I think the new profile revealed some graphics issues. This bug is already in the Graphics component, so no need to create a separate bug.

Comment 16

[alex_mayorga]

¡Hola Sean!

I tried Google Meet again today and although it was a little better it would still hang at times.

I managed to capture a new profile at https://share.firefox.dev/2RLNkBe in case it is useful.

Please let me know if this should be a separate bug.

¡Gracias!
Alex

Comment 17

[alex_mayorga]

¡Hola Sean!

Another one from today when Google Meet in fact said that the connection was completely lost and had to reconnect to the meeting:

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

Hope this is useful on pinning down the problem.

¡Gracias!
Alex

Comment 18

[Sean Feng [:sefeng]]

Hmm, I noticed the hangs were caused by webrtc::RtcpObserver::LastProcessedRtt, this seems to be a webrtc issue.

Comment 19

[Sean Feng [:sefeng]]

Randell, do you mind check the above profile and see if anything abnormal?

Comment 20

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

The problem seems to be an almost-deadlock waiting for PollStats(), which is waiting on a critical section for 19 seconds

Alex, was about:webrtc open? Does this machine have an intrusive AV/etc service like Black Carbon installed?

Comment 21

[alex_mayorga]

¡Hola Randell!

I'm just today learning of about:webrtc so it is very unlikely that that was at play at the time.

Carbon Black Cloud Sensor 64-bit 3.6.0.2076 is installed on this device.

If this is believed to be the root of the issues perhaps it is related to
https://bugzilla.mozilla.org/show_bug.cgi?id=1707762
as well.

Please let me know if there's anything else I should try or that you need me to collect form the profile or device.

¡Gracias!
Alex

Comment 22

[Jim Mathies [:jimm]]

This (hopefully) was addressed by the webrtc update in 97. Please reopen and ni me if you're still seeing this.