dbc2ba2026
In rare cases, it is possible to queue a call to SendData from the signaling thread on a channel being closed or already closed in the network thread. By keeping track of currently open streams, we avoid sending messages with a stream id of channels that the other side already considers closed and has already reused for a new channel. This caused rare messages to be delivered on the wrong data channel if a message was quickly sent, channel closed and a new one reopened. Bug: webrtc:14277 Change-Id: If35fed8d12d5d2c18cdc6601085d8b632c37a0ba Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/272624 Commit-Queue: Florent Castelli <orphis@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#37880}
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