Only create H264 frames if there are no gaps in the packet sequence number.

Only create H264 frames if there are no gaps in the packet sequence number.

In the case of H264 we can't know which packet that is the fist packet of a
frame. In order to avoid creating incomplete frames we keep track of which
packets that we haven't received, and if there is a gap in the packet sequence
number leading up to this frame then a frame wont be created.

BUG=chromium:716558
R=holmer@google.com, stefan@webrtc.org

Review-Url: https://codereview.webrtc.org/2926083002
Cr-Original-Commit-Position: refs/heads/master@{#18559}
Review-Url: https://codereview.webrtc.org/2947373002 .
Cr-Commit-Position: refs/branch-heads/60@{#5}
Cr-Branched-From: c61bf947b4ac31f3500858ffcae6fee39d799930-refs/heads/master@{#18252}
Committed: https://chromium.googlesource.com/external/webrtc/+/86c2c61b5099eaa8107b4bfd5635495055844a12

[philipel, 2017-06-22 09:18:56]

philipel@webrtc.org changed reviewers:
+ stefan@webrtc.org

[philipel, 2017-06-22 09:18:57]

Merge to M60

[holmer, 2017-06-22 09:21:48]

holmer@google.com changed reviewers:
+ holmer@google.com

[holmer, 2017-06-22 09:21:49]

lgtm

[stefan-webrtc, 2017-06-22 09:25:09]

lgtm

[philipel, 2017-06-22 09:26:54]

Description was changed from

==========
Only create H264 frames if there are no gaps in the packet sequence number.

In the case of H264 we can't know which packet that is the fist packet of a
frame. In order to avoid creating incomplete frames we keep track of which
packets that we haven't received, and if there is a gap in the packet sequence
number leading up to this frame then a frame wont be created.

BUG=chromium:716558

Review-Url: https://codereview.webrtc.org/2926083002
Cr-Commit-Position: refs/heads/master@{#18559}
(cherry picked from commit 2c9f9f2bc9dbbb6f8abeb92615b42ce0ddfccb39)
==========

to

==========
Only create H264 frames if there are no gaps in the packet sequence number.

In the case of H264 we can't know which packet that is the fist packet of a
frame. In order to avoid creating incomplete frames we keep track of which
packets that we haven't received, and if there is a gap in the packet sequence
number leading up to this frame then a frame wont be created.

BUG=chromium:716558
R=holmer@google.com, stefan@webrtc.org

Review-Url: https://codereview.webrtc.org/2926083002
Cr-Original-Commit-Position: refs/heads/master@{#18559}
Review-Url: https://codereview.webrtc.org/2947373002 .
Cr-Commit-Position: refs/branch-heads/60@{#5}
Cr-Branched-From:
c61bf947b4ac31f3500858ffcae6fee39d799930-refs/heads/master@{#18252}
Committed:
https://chromium.googlesource.com/external/webrtc/+/86c2c61b5099eaa8107b4bfd5...
==========

[philipel, 2017-06-22 09:26:55]

Committed patchset #1 (id:1) manually as
86c2c61b5099eaa8107b4bfd5635495055844a12 (presubmit successful).