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

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

List of changes in WebRTC:

https://webrtc.googlesource.com/src/+log/ef43aafcf5953845b71840e14c94942d60c541c1..d78323faba860af234a00eb70d0dc02cb484fffc?pretty=fuller&n=10000

My best guess is:

https://webrtc.googlesource.com/src/+/fc9c4e88b5569f0d2cd1c64cbc27fd969ce2db17

+aleloi and philipel in case this one is involved:

https://webrtc.googlesource.com/src/+/32134470cacefecc27d59a0086aed71f9663404b

This bug has an owner, thus, it's been triaged. Changing status to "assigned".

ClusterFuzz has detected this issue as fixed in range 591170:591178.

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

Fuzzer: afl_rtp_frame_reference_finder_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900004478
Crash State:
  absl::raw_logging_internal::RawLog
  absl::variant_internal::ThrowBadVariantAccess
  webrtc::RTPVideoHeaderVP9& absl::variant_internal::TypedThrowBadVariantAccess<we
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=574469:574477
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=591170:591178

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

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 6035607269408768 is verified as fixed, so closing issue as verified.

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