commit | 4cb5b64b16deeb1cb22141ad104ed83ff4899624 | [log] [tgz] |
---|---|---|
author | Taylor Brandstetter <deadbeef@webrtc.org> | Fri Aug 12 10:10:31 2016 -0700 |
committer | Taylor Brandstetter <deadbeef@webrtc.org> | Fri Aug 12 17:10:42 2016 +0000 |
tree | c34ef76af1c4c7aef457c8eca00dc963582fb083 | |
parent | 64a7eab89183845e4a295c512bcf1c87a2424f86 [diff] |
Fix for data channels perpetually stuck in "closing" state. If the data transport is destroyed while data is buffered (due to the PC being closed, or a description set with data rejected), the data channel was getting stuck in a "closing" state, waiting to finish sending its buffered data. But since there's no more transport, it will never get another chance to send buffered data. It just needs to terminate non-gracefully and discard the buffered data in this situation. R=skvlad@webrtc.org, zhihuang@webrtc.org Review URL: https://codereview.webrtc.org/2235843003 . Cr-Commit-Position: refs/heads/master@{#13737}
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.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.