Closed Bug 1339270 Opened 8 years ago Closed 8 years ago

Upstream webrtc code doesn't add padding packets to retransmission history (Issue 7143)

Categories

(Core :: WebRTC: Networking, defect, P1)

45 Branch
defect

Tracking

()

RESOLVED FIXED
mozilla54
Tracking Status
firefox-esr45 --- wontfix
firefox51 --- wontfix
firefox52 --- affected
firefox-esr52 --- affected
firefox53 --- affected
firefox54 --- fixed

People

(Reporter: jesup, Assigned: jesup)

Details

Attachments

(1 file)

Upstream code in webrtc.org branch 49 and 57 (and 43) don't add padding packets (RTPSender::SendPadData()) to the rtp packet history. If one of the padding packets is lost, it can't be retransmitted, and the other side's jitter buffer will still until the next keyframe, or until it times out waiting for a retransmit and requests a keyframe. This causes freezes and lower video quality. Webrtc.org issue 7143: https://bugs.chromium.org/p/webrtc/issues/detail?id=7143
Rank: 15
this also causes the simulcast tests to be flaky under rr, for example
Attachment #8836923 - Flags: review?(na-g)
Attachment #8836923 - Flags: review?(na-g) → review+
Pushed by rjesup@wgate.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/b6bdf4cf8348 Add rtp 'padding' packets into rtp history for handling NACKs r=ng
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
See Also: → 1337810
See Also: 1337810
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: