d5f50a1b53
In some situation, typically when incoming packets were reordered, the DelayPeakDetector::Update method may be called twice (or more) with non-zero inter_arrival_time argument, but without the TickTimer object being updated in between (i.e., packets coming in more or less at the same time). In these situations, a delay peak may be registered with zero peak period. This could eventually trigger the DCHECK in DelayPeakDetector::MaxPeakPeriod(). With this fix, the problem is solved by not registering peaks for which the TickTimer object has not moved since the last peak. The problem was originally introduced with https://codereview.webrtc.org/1921163003. BUG=webrtc:6021 Review-Url: https://codereview.webrtc.org/2085233002 Cr-Commit-Position: refs/heads/master@{#13257}
Name: WebRTC URL: http://www.webrtc.org Version: 90 License: BSD License File: LICENSE Description: WebRTC provides real time voice and video processing functionality to enable the implementation of PeerConnection/MediaStream. Third party code used in this project is described in the file LICENSE_THIRD_PARTY.