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}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others. This page is maintained by the Google Chrome team.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc