848980198e
Both CaptureFrame() and ProcessBuffer() hold a lock over the frame queue and it happens that one waits for the other, causing unnecessary delays since we already work with a queue having two frames, but this way we don't really need a queue. Instead, keep reference to the last processed buffer, which we will always use in CaptureFrame() and update it every time at the end of ProcessBuffer(). This avoid unnecessary waiting for the lock over the queue to be released. Bug: chromium:333945842 Change-Id: I4afeb1daacd342e92578a50ac6e1c89a691bb8f8 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/350042 Commit-Queue: Jan Grulich <grulja@gmail.com> Reviewed-by: Alexander Cooper <alcooper@chromium.org> Reviewed-by: Mark Foltz <mfoltz@chromium.org> Cr-Commit-Position: refs/heads/main@{#42394}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation