9cbebee523
Currently, VideoCapturerAndroid sets the thread and handler in the ctor and clears them in dispose(). This CL sets the handler in startCapture() instead and clears it in stopCapture(). The purpose is to prepare for sending in the SurfaceTextureHelper in startCapture() instead of letting VideoCapturerAndroid create it in the ctor. All access to the handler is now synchronized by a lock, and all Runnables are posted with a token so that they can be removed all at once in stopCapture() to guarantee that no pending operation will be executed after stopCapture(). BUG=webrtc:5519 Review URL: https://codereview.webrtc.org/1763673002 Cr-Commit-Position: refs/heads/master@{#11939}
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