1653112 - Google Meet video call hanged and developer tools became unusable

Status: NEW

(Core :: WebRTC: Audio/Video, defect, P3)

Description

[alex_mayorga]

¡Hola!

So I was in a long running Google Meet video call (8+ hours) due to WFH.

The tab hanged and became impossible to debug with Dev Tools.

Managed to capture https://share.firefox.dev/3j9hYxZ

Starting with this component, but I might be completely wrong so please re-triage as needed.

¡Gracias!
Alex

Comment 1

[alex_mayorga]

Attachment: Screen capture of the hung tab

Comment 2

[Nico Grunbaum [:ng, @chew:mozilla.org]]

Paul, I am not sure if you are the right person to ask, so feel free to redirect the NI, but could you look at the perf capture? Besides there being 1-2 second GC segments, the Graph Runner is reporting a latency of several minutes.

Comment 3

[Paul Adenot (:padenot)]

I had a look. The whole process is frozen. I'm asking for help in 1653113.

Comment 4

[Patricia Lawless]

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

Comment 5

[alex_mayorga]

¡Hola Paul!

Hope these lines find you well.

I had another case of frozen video feeds in "El Goog"'s Meet today in the latest Nightly.

Here's a profile FWIW: https://share.firefox.dev/3BHzamK

Please let me know if y'all need anything from the device or profile.

¡Gracias!
Alex

Comment 6

[Paul Adenot (:padenot)]

We see in the DecodingThread (three difference threads) that the function is hitting the max timeout for waiting for a frame, and then presumably exits.

So it seems like key frames have been requested, but never arrive (FIR, PLI).

Do we know of anything in the area that looks like it? It will be important to test this after the uplift.