632cd9bb03
PacketBuffer takes RtpVideoHeader struct as an input that is complicated and hard to fuzz. Current PacketBuffer doesn't fuzz it and thus has very low coverage. RtpVideoFrameAssembler uses PacketBuffer underneath and takes as input almost raw rtp packet and thus easier to fuzz and better match production input Bug: webrtc:7408 Change-Id: I00394c35e002a667760eed477f11ac7898f7eacc Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/290574 Commit-Queue: Danil Chapovalov <danilchap@webrtc.org> Reviewed-by: Philip Eliasson <philipel@webrtc.org> Cr-Commit-Position: refs/heads/main@{#39013}
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