f9e116f46e
When resetting several streams in sequence, only the first stream will be included in the first RE_CONFIG chunk as it's created eagerly whenever someone calls ResetStreams. The remaining ones are queued as pending. When the first request finishes, the remaining ones should continue to be processed, but this wasn't done prior to this commit. This would only happen if two streams would be reset with shorter time between them than a RTT, so that there would be an outstanding request forcing the second reset to be enqueued. Bug: chromium:1312009 Change-Id: Id74b375d1d1720406a3bca4ec60df5780ca7edba Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/257306 Reviewed-by: Florent Castelli <orphis@webrtc.org> Commit-Queue: Victor Boivie <boivie@webrtc.org> Cr-Commit-Position: refs/heads/main@{#36404}
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.
Development
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation