cbaa254641
I found one additional way a crash could occur: "OnRtpTransportChanged" being called instead of "OnDtlsTransportChanged", due to a mixup of m= section types. I could reproduce this by: 1. Applying description with RTP data channel m= section. 2. Applying description with both a rejected RTP data channel m= section and rejected SCTP m= section. This is a very strange scenario, but maybe there are other ways to reproduce that I haven't thought of. The solution is to combine "OnRtpTransportChanged" and "OnDtlsTransportChanged", and not do anything with the content type. This simplifies the code a bit as well. Bug: chromium:827917 Change-Id: If6818ea0c41573255831534060b30c76a6544e04 Reviewed-on: https://webrtc-review.googlesource.com/70360 Reviewed-by: Zhi Huang <zhihuang@webrtc.org> Commit-Queue: Zhi Huang <zhihuang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22893}
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