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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/f022b8fb8db35e20d59702a3ba5ed3a9dc13c516 (Tidy up redundant call chain of CallbackBufferSize).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Since this is something about MPEG, I would like Dale to take a look at it.

I've looked at the CF's repro case and it just looks like a random data file. Also the suspected CL of mine was a simple renaming in WebAudio which has nothing to do with MPEG.

ClusterFuzz has detected this issue as fixed in range 570151:570153.

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

Fuzzer: libFuzzer_media_es_parser_mpeg1audio_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  media_es_parser_mpeg1audio_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=570080:570081
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=570151:570153

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

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

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