commit | 096ad02c02b4bc6c046282b8793ef84d041dd0d8 | [log] [tgz] |
---|---|---|
author | Evan Shrubsole <eshr@google.com> | Mon May 24 14:06:09 2021 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 24 14:06:19 2021 |
tree | 1d0c839a5382033907597f6a893f5d81a5e6de6a | |
parent | 2fa477406771a09b2276085cdeb0f5a12ee961a0 [diff] |
Revert "Fix race between enabled() and set_enabled() in VideoTrack." This reverts commit 5ffefe9d2d743c66f8a8bcbc5ad9662a3138840a. Reason for revert: Breaks Chromium Android browser tests on fyi bots. Original change's description: > Fix race between enabled() and set_enabled() in VideoTrack. > > Along the way I introduced VideoSourceBaseGuarded, which is equivalent > to VideoSourceBase except that it applies thread checks. I found that > it's easy to use VideoSourceBase incorrectly and in fact there appear > to be tests that do this. > > I made the source object const in VideoTrack, as it already was in > AudioTrack, and that allowed for making the GetSource() accessors > bypass the proxy thread hop and give the caller direct access. > > Bug: webrtc:12773, b/188139639, webrtc:12780 > Change-Id: I022175c4239a1306ef54059c131d81411d5124fe > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/219160 > Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> > Reviewed-by: Andrey Logvin <landrey@webrtc.org> > Commit-Queue: Tommi <tommi@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#34096} TBR=mbonadei@webrtc.org,tommi@webrtc.org,landrey@webrtc.org,webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: I16323d459c76eb6a87cc602a0048f6ee01c81626 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:12773 Bug: b/188139639 Bug: webrtc:12780 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/219637 Reviewed-by: Evan Shrubsole <eshr@google.com> Commit-Queue: Evan Shrubsole <eshr@google.com> Cr-Commit-Position: refs/heads/master@{#34101}
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.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.