20e8cfb341
The issue occurred if a control segment is received after a non-control segment received out-of-order, which only happens if: * The initial "connect" segment is lost, and retransmitted later. * Both sides send "connect"s simultaneously (rather than having designated server/client roles), such that the local side thinks a connection is established even before its "connect" has been acknowledged. * Nagle algorithm disabled, allowing a data segment to be sent before the "connect" has been acknowledged. This may seem like a pretty specific set of circumstances, but it can happen with chromoting. See the linked bug for more details. Bug: webrtc:9208 Change-Id: I3cfe26e02158fcc5843f32d4e2ef7c511d58d9c9 Reviewed-on: https://webrtc-review.googlesource.com/78861 Reviewed-by: Sergey Ulanov <sergeyu@google.com> Reviewed-by: Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org> Cr-Commit-Position: refs/heads/master@{#23477}
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 http://www.webrtc.org/native-code/development 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: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct