7a284e1614
What steps will reproduce the problem? 1. Connect a TCPPort, creating a TCPConnection 2. Disconnect the interface (e.g turn it off in android) 3. Send Ping on the TCPConnection Crash. The TCPConnection calls FailAndPrune when it fails to reconnect the TCPConnection. FailAndPrune which removes the StunRequests. When this is called from the Ping() code, that will still access the StunRequest after the call to the Connection. Solution: Instead of calling FailAndPrune deep down in the Ping()-stack post a message to self to do this with a "clean" stack instead. BUG: webrtc:11315 Change-Id: Id328b1b7c92311fa5b9adbfd2eb1dd14bf19805d Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/167522 Commit-Queue: Jonas Oreland <jonaso@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Qingsi Wang <qingsi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30389}
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