commit | 382a72a0d321f19ac9cdc9bb30712cefe2639f88 | [log] [tgz] |
---|---|---|
author | ilnik <ilnik@webrtc.org> | Mon Mar 13 01:54:13 2017 -0700 |
committer | Commit bot <commit-bot@chromium.org> | Mon Mar 13 08:54:13 2017 +0000 |
tree | fe462c90a7ddae190b034aa0aaebb2883c1129aa | |
parent | ff2ebf5e3074b3b0716e9c9ad1336ab4db1e1cf8 [diff] |
Revert of rewrite frame generator capturer to use TaskQueue instead of EventTimeWrapper (patchset #2 id:90001 of https://codereview.webrtc.org/2744003002/ ) Reason for revert: CallPerfTest.ReceivesCpuOveruseAndUnderuse perf test fails due to this CL. It requires very accurate frame rate, which may not be so accurate now. Original issue's description: > Reland of rewrite frame generator capturer to use TaskQueue instead of EventTimeWrapper (patchset #1 id:1 of https://codereview.webrtc.org/2743993002/ ) > > And enable large full-stack test depending on that change (Reland of https://codereview.webrtc.org/2741823003/) > TBR=stefan@webrtc.org,tommi@webrtc.org > BUG=webrtc:7301,webrtc:7325 > > Review-Url: https://codereview.webrtc.org/2744003002 > Cr-Commit-Position: refs/heads/master@{#17196} > Committed: https://chromium.googlesource.com/external/webrtc/+/8c0a5896d1cdc7bb81307c33fa4b3538d8160a0f TBR=stefan@webrtc.org,tommi@webrtc.org,sprang@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:7301,webrtc:7325 Review-Url: https://codereview.webrtc.org/2748643002 Cr-Commit-Position: refs/heads/master@{#17198}
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.