Closed Bug 1817096 Opened 1 year ago Closed 1 year ago

Intermittent failure in RTCPeerConnection-getStats.https.html related to inbound-rtp stats

Categories

(Core :: WebRTC: Signaling, defect, P3)

defect

Tracking

()

RESOLVED FIXED
113 Branch
Tracking Status
firefox113 --- fixed

People

(Reporter: bwc, Assigned: bwc)

References

(Blocks 1 open bug)

Details

Attachments

(2 files, 1 obsolete file)

This test has not been running for some time due to a timeout in a preceding test-case, but it seems to be flaky for some reason.

After some experimentation, it seems that this is the culprit:

https://searchfox.org/mozilla-central/rev/dbec4165e4c26a0ff970b614842b689e8357593c/dom/media/webrtc/transportbridge/MediaPipeline.cpp#588,600

Here we are invoking the callback that triggers unmute before passing the packet on to libwebrtc. I think that in some situations, the unmute event arrives in JS, and JS can turn around and call getStats, before the RTP packet is queued up for libwebrtc. Making the call to OnRtpPacketReceived after we send the packet to libwebrtc seems to make this test-case work reliably.

Assignee: nobody → docfaraday
Attachment #9323116 - Attachment is obsolete: true
Pushed by bcampen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3d678f5ba6a3
Bring the blocking of unmute events in line with the spec. r=mjf
https://hg.mozilla.org/integration/autoland/rev/b89b9564bb4b
Drive unmute from the conduit (on call thread) instead of the pipeline (on STS). r=pehrsons
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/39260 for changes under testing/web-platform/tests
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
Upstream PR merged by moz-wptsync-bot
Blocks: 1822350
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: