Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically adding ccs based on suspected regression changelists:

Fuzzing for video_coding::FrameBuffer2. by philipel@webrtc.org - https://webrtc.googlesource.com/src/+/1e9cf7faf8c979066679307a77c753f7cab597eb

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

ClusterFuzz has detected this issue as fixed in range 566730:566735.

Detailed report: https://clusterfuzz.com/testcase?key=6374076680241152

Fuzzer: libFuzzer_frame_buffer2_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  webrtc::video_coding::FrameBuffer::NextFrame
  webrtc::FuzzOneInput
  webrtc_fuzzer_main.cc
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=559597:559618
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=566730:566735

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6374076680241152

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6374076680241152 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.