65f47275cb
This really only happens on the memcheck bot. But the issue is that the render thread may be started before the timer is started on the main thread, which incorrectly attaches the timer to the render thread. Then a thread check assertion occurs when the timer is stopped on the main thread. Simply starting the timer before starting the render thread fixes this. BUG=webrtc:6062 TBR=tommi@webrtc.org Review URL: https://codereview.webrtc.org/2105013002 . Cr-Commit-Position: refs/heads/master@{#13317}
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