Screen sharing hung on https://meet.google.com/
Categories
(Core :: WebRTC, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox88 | --- | affected |
People
(Reporter: alex_mayorga, Unassigned)
References
(Blocks 2 open bugs, )
Details
(Keywords: nightly-community, Whiteboard: [wfh])
¡Hola y'all!
A screen sharing hung Firefox Nightly pretty badly for me today.
Managed to capture a profile over at https://share.firefox.dev/2NWZ55W
Hope this is helpful on finding the root cause.
Please let me know if there's anything needed form the affected Firefox Nightly.
¡Gracias!
Alex
|
Reporter | |
Updated•4 years ago
|
|
||
Comment 1•4 years ago
|
||
¡Hola Alex! Thank you for the bug report! I went through the profile and I didn't see any obvious, although I'm not an expert at reading those, so hopefully someone else can have a look as well.
One possibility is that you hit a deadlock, where two parts of Firefox are waiting on each other and nothing happens. In that case, Firefox will hang, but you won't see symptoms of a performance problem, like 100% CPU usage. Was your machine acting like there was a performance problem, or was Firefox just not responding?
¡Muchas gracias!
|
||
Comment 2•4 years ago
|
||
Alex, thanks again for another bug report. I have a couple of follow up questions: did the hang occur at the end of the call or perhaps as someone was leaving? If not, how long would you estimate you had been in the call?
|
|
Reporter | |
Comment 3•4 years ago
|
||
¡Hola Nico!
did the hang occur at the end of the call or perhaps as someone was leaving?
Memory fails me here, sorry. I don't really recall if this was related to someone leaving.
how long would you estimate you had been in the call?
My calendar shows that I had 4 30 minute meetings and 1 1 hour meeting that day.
But we also have an overarching meeting that last over the 8 hours of our workday on which we share things ad hoc.
Memory fails me here too, sorry.
Next time I will be more mindful of collecting these details.
Please let me know if there's a test I could run or any further information I can collect to make this report more actionable.
¡Gracias!
Alex
|
||
Updated•4 years ago
|
|
|
||
Comment 4•4 years ago
|
||
Setting this to P1 for investigation and analysis so we can determine its true impact to the user.
|
||
Comment 5•3 years ago
|
||
Alex, have you experienced this issue recently? Our libwebrtc update landed a few weeks ago.
|
|
||
Comment 6•3 years ago
|
||
I'm going to close this as resolved/inactive since we've gone 2 weeks without a reply and many months of prior inactivity.
Description
•