commit | 35d052c2a3c5fa5d4bc4501a8b4d3f36c3d3201d | [log] [tgz] |
---|---|---|
author | JT Teh <jtteh@webrtc.org> | Thu Mar 29 22:20:00 2018 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Mar 30 00:49:48 2018 +0000 |
tree | 0b7f9177a99338b8eb228c0cee82ce69ec2de374 | |
parent | adad657790166ee18aadd8e2a7164adffb5ba409 [diff] |
Revert "Add unit tests for RTCCVPixelBuffer and ObjCVideoTrackSource." This reverts commit 4ea50c2b421ae3e40d1d02b8eb8c5802288b181e. Reason for revert: This change is causing crashes in video calls. RTCCVPixelBuffer.mm - line 120 Compare is asserting as 420f is not 420v Original change's description: > Add unit tests for RTCCVPixelBuffer and ObjCVideoTrackSource. > > This CL also fixes a couple of bugs found in the toI420 method for > RTCCVPixelBuffers backed by RGB CVPixelBuffers. > > Bug: webrtc:9007 > Change-Id: I19ab8177f4b124a503cfda9f0166bd960f668982 > Reviewed-on: https://webrtc-review.googlesource.com/64940 > Commit-Queue: Anders Carlsson <andersc@webrtc.org> > Reviewed-by: Kári Helgason <kthelgason@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#22656} TBR=andersc@webrtc.org,kthelgason@webrtc.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: webrtc:9007 Change-Id: I500514ce05dd0555f8c4a05010ad52bd67c2fed3 Reviewed-on: https://webrtc-review.googlesource.com/65561 Commit-Queue: JT Teh <jtteh@webrtc.org> Reviewed-by: JT Teh <jtteh@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22686}
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 http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.