Closed Bug 1639976 Opened 5 years ago Closed 3 years ago

Poor performance during a Zoom call

Categories

(Core :: WebRTC, defect, P1)

Product:
Core
Component:
WebRTC
Version:
78 Branch
Platform:
x86_64
Windows 10
Type:
defect

Tracking

()

Status:
RESOLVED INACTIVE
Tracking Flags:
Tracking Status
firefox-esr68 --- wontfix
firefox77 --- wontfix
firefox78 --- wontfix
firefox79 --- wontfix
firefox81 --- wontfix
firefox82 --- wontfix
firefox83 --- wontfix
firefox88 --- wontfix
firefox89 --- wontfix
firefox90 --- wontfix

People

(Reporter: alex_mayorga, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

(Keywords: nightly-community, Whiteboard: [wfh])

¡Hola!

Had some terrible performance during a Zoom call with today's Firefox Nightly.

Managed to capture https://perfht.ml/3bTMTJw

Filing this report in case it is useful.

¡Gracias!
alex

Whiteboard: [wfh]
Component: Audio/Video → WebRTC

Byron, any thoughts?

Flags: needinfo?(docfaraday)

The content process running zoom seems to be spending all of its time in mozilla::detail::EventQueueInternal::PutEvent, and only a tiny minority of that time is being spent in the actual work that function does (mozilla::Queue::Push). That says we're spending tons of time in here:

https://searchfox.org/mozilla-central/rev/bc3600def806859c31b2c7ac06e3d69271052a89/xpcom/threads/EventQueue.cpp#23-32

That's gecko profiler code. Has this problem ever happened when you were not running the gecko profiler?

Flags: needinfo?(docfaraday) → needinfo?(alex_mayorga)

¡Hola Byron!

I ran the profiler in the hopes of capturing the terrible performance in Zoom and give y'all something actionable.

The Zoom call was bad even before the profiling started.

With that said I caved and ended up installing the Zoom client.

If useful I could get on a Zoom call with someone and troubleshoot live if it helps things.

Would you be interested on that?

¡Gracias!
Alex

Flags: needinfo?(alex_mayorga) → needinfo?(docfaraday)

Was this a video call? I cannot get zoom to capture video at all, either on nightly or release.

Flags: needinfo?(docfaraday) → needinfo?(alex_mayorga)

¡Hola Byron!

Yes, this was a video call.

¡Gracias!
Alex

Flags: needinfo?(alex_mayorga)

Ok. I've filed bug 1643038 for the video capture problem. Is video capture working for you at all right now?

Flags: needinfo?(alex_mayorga)
Severity: -- → S2
Priority: -- → P2

¡Hola Byron!

I've tested over at https://zoom.us/test and I can see my own video albeit it seems to refresh rather slowly IMHO.

Here's the profile of the whole interaction in case it is useful:

https://share.firefox.dev/30eaLpf

Please let me know if there's anything else I could provide to assist on your investigation.

¡Gracias!
Alex

Flags: needinfo?(alex_mayorga)

¡Hola y'all!

Tried again today and the issue is still there.

A fresh profile at https://share.firefox.dev/2RWCDc8

Please let me know if anything is needed from the affected system.

¡Gracias!
Alex

status-firefox81: --- → affected
status-firefox82: --- → affected
status-firefox83: --- → affected
Severity: S2 → S3
Blocks: webrtc-perf

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

Priority: P2 → P1

¡Hola y'all!

Tried again today and the issue is still there i.e. there's high CPU usage and the laptop fan gets loud.

A fresh profile at https://share.firefox.dev/3upBQSB

Please let me know if anything is needed from the affected system.

¡Gracias!
Alex

URL: https://<workplace>.zoom.us → https://zoom.us/test
status-firefox88: --- → affected
status-firefox89: --- → affected
status-firefox90: --- → affected

Alex, I'm curious to know if you see any improvement on Nightly v96. I've tried it locally and it seems to make some difference, but I'm in a VM so I don't know if that translates to an improvement you'll see.

Flags: needinfo?(alex_mayorga)

I'm going to close this as resolved/inactive since we've gone 2 weeks without a reply and many months of prior inactivity.

Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(alex_mayorga)
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.