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

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

Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.
Thank You.

ClusterFuzz has detected this issue as fixed in range 619089:619096.

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

Fuzzer: libFuzzer_media_vp9_parser_encrypted_fuzzer
Fuzz target binary: media_vp9_parser_encrypted_fuzzer
Job Type: x86_libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  size >= 0 in bit_reader.cc
  media::BitReader::BitReader
  media::Vp9RawBitsReader::Initialize
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan_debug&range=619089:619096

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

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

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

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