ac025898e1
Earlier CLs assumed that the object pointed to by call_ had to be accessed on the worker thread. While this is generally the case, Call::MediaTransportChange is explicitly thread safe, so PeerConnection::OnTransportChanged doesn't have to run on the worker thread for that reason. Which is fortunate, because it actually runs on the network thread. The RTC_RUN_ON(worker_thread()) annotation on the method declaration was ineffective because this method is being called via a base class pointer; replacing it with a call to RTC_DCHECK_RUN_ON(worker_thread()) in the function body immediately triggered assertions in the unit tests. Bug: webrtc:9987 Change-Id: I08cf558a74f4ca2b2eff8ef4810ebbd1287a9726 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/129442 Commit-Queue: Karl Wiberg <kwiberg@webrtc.org> Reviewed-by: Steve Anton <steveanton@webrtc.org> Cr-Commit-Position: refs/heads/master@{#27287}
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