| commit | 57db65255cc6004e3d82225fa4d2df565f169497 | [log] [tgz] |
|---|---|---|
| author | perkj <perkj@webrtc.org> | Fri Apr 08 15:16:33 2016 |
| committer | Commit bot <commit-bot@chromium.org> | Fri Apr 08 15:16:41 2016 |
| tree | 07d15f405ffb65b5acdabe3526340015019746ec | |
| parent | babf8ee78c87f8965f2883b09d3dede6e3e3e247 [diff] |
Changed PeerConnectionEndToEndTest to use a separate worker thread. This is a follow up to https://codereview.webrtc.org/1859933002 to change this test also to use a separate worker thread. PeerConnectionEndToEndTest currently use the current thread both as a signaling thread and a worker thread. Although convenient while debugging, it can also hide real bugs. An example is https://codereview.webrtc.org/1766653002/#ps420001 where the worker thread is deadlocked in the track proxy due to that the worker thread waits for the signaling thread but the proxy in turns invokes the worker thread..... That bug was only discovered on Android. BUG= webrtc:5426 Review URL: https://codereview.webrtc.org/1860423002 Cr-Commit-Position: refs/heads/master@{#12295}
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.