4cb5b64b16
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.
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