1812134 - Low outbound-rtp FPS sent on meet.google.com in Beta (110)

Status: RESOLVED DUPLICATE of bug 1812293

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

Description

[Bruce Ricketts]

Attachment: WebRTC data from the bugged client, captured after video is re-enabled (notice that the outbound RTP streams have slowed to 0KBps)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/110.0

Steps to reproduce:

This bug affects Firefox Beta 110, and was introduced in this nightly build: https://ftp.mozilla.org/pub/firefox/nightly/2022/12/2022-12-14-16-24-11-mozilla-central/

The issue is not present on Firefox <= 109.

To reproduce:

1. User A: navigate to meet.google.com and log in.
2. User A: click "New Meeting" -> "Start an instant meeting" (allow access to camera and mic).
3. User A: once the meeting starts, copy the ten-letter code at the bottom-left of the meeting window.
4. User B: open a new window in any browser and navigate to meet.google.com (the same account can be used, it does not affect repro).
5. User B: In the "Enter a code or nickname" field, paste the copied ten-letter code and join the meeting.
6. User A: toggle video by clicking the video-camera icon twice.

Occasionally, the same results can be achieved without step 6.

Actual results:

User A's video stream appears frozen or blank to User B. WebRTC data from about:webrtc (attached) shows very low outgoing frame rate and count under PeerConnection stats, leading us to believe this is not a Meet issue.

Expected results:

User A's video stream be visible to User B.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::WebRTC: Audio/Video' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Jim Mathies [:jimm]]

regression range - https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=300b0ac8eb7be542901c94bd85ad5d82481ec03f&tochange=7ff758e0d08b4bdf0ce3bd2abe84a1bff3be8ff4

Comment 3

[Byron Campen [:bwc]]

This looks like a dupe of bug 1812293.

Comment 4

[Bruce Ricketts]

Confirmed fixed in Nightly 111.0a1 (2023-02-01)