Closed Bug 1736434 Opened 3 years ago Closed 3 years ago

Google Meet call receiving video at very low framerate

Categories

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

ARM64
macOS
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: overholt, Unassigned)

References

Details

Twice in the past week I've been on Google Meet calls with another party who had a solid internet connection but I was receiving video at a very low framerate on my similarly solid internet connection. Audio seemed to keep coming through fine but video would be received in bursts of decent framerates interspersed with multiple seconds of freezes. I couldn't capture a log due to bug 1736432 but I'm happy to try to reproduce live if someone would like.

My setup: Nightly on macOS Big Sur (11.6), Apple M1 MacBook Air 16 GB

See Also: → 1736432
OS: Unspecified → macOS
Hardware: Unspecified → ARM64

It's possible the webrtc lib update may help here, and we also have some outstanding questions to Google about what their service is doing that might play a role.

If you have time and want to try testing with the libwebrtc update work-in-progress, you can find a binary here:

https://treeherder.mozilla.org/jobs?repo=try&revision=c854d8f688e04aed12aac18aafbe739045cd8ffb&selectedTaskRun=E0r8QeSqR9CyjYMhaQlLdQ.0

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

(In reply to Byron Campen [:bwc] from comment #2)

If you have time and want to try testing with the libwebrtc update work-in-progress, you can find a binary here:

https://treeherder.mozilla.org/jobs?repo=try&revision=c854d8f688e04aed12aac18aafbe739045cd8ffb&selectedTaskRun=E0r8QeSqR9CyjYMhaQlLdQ.0

For some reason the DMG says "Firefox Nightly" is damaged and can't be opened. You should eject the disk image. What am I doing wrong?

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

Weird... Michael, you seeing the same thing?

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

(In reply to Byron Campen [:bwc] from comment #4)

Weird... Michael, you seeing the same thing?

It's apparently a known thing because we're not notarizing try builds. One can change security settings on a Mac to bypass. I'll try that.

Flags: needinfo?(mfroman)

Yes, sorry - I forgot that try builds for M1 are a bit of a mess because of signing issues.

The uplift has landed, let us know if this still happens.

No longer blocks: webrtc-triage
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.