| commit | 7946b546db74d0af2badd1002eaab01ed837b194 | [log] [tgz] |
|---|---|---|
| author | terelius <terelius@webrtc.org> | Mon Jan 02 21:44:49 2017 |
| committer | Commit bot <commit-bot@chromium.org> | Mon Jan 02 21:44:49 2017 |
| tree | 37a7b61ac61bc488472126ac51538b83b386ff63 | |
| parent | 33985e125b041c3b843dd9e514e4380413f5ab96 [diff] |
Revert of Added first layer of the echo canceller 3 functionality (patchset #13 id:240001 of https://codereview.webrtc.org/2584493002/ ) Reason for revert: Memcheck buildbot detected memory leaks in the death tests. The code looks fine to me, but please investigate what causes the error and reland. Original issue's description: > Added first layer of the echo canceller 3 functionality. > > This CL adds the first layer of the echo canceller 3. > All of the code is as it should, apart from > block_processor.* which only contains placeholder > functionality. (Upcoming CLs will add proper > functionality into those files.) > > > > BUG=webrtc:6018 > > Review-Url: https://codereview.webrtc.org/2584493002 > Cr-Commit-Position: refs/heads/master@{#15861} > Committed: https://chromium.googlesource.com/external/webrtc/+/38fd1758e90bcdc7690a552e7ef0ec0d143d2f30 TBR=ivoc@webrtc.org,aleloi@webrtc.org,henrik.lundin@webrtc.org,peah@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:6018 Review-Url: https://codereview.webrtc.org/2603293002 Cr-Commit-Position: refs/heads/master@{#15877}
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.