Predator could not provide any possible suspects.

From the below CL observing some changes related to 'pipeline_integration_fuzzertest.cc' , hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/dfe573b3621abc60d458ef675580ee3ba25d8de7..c4ccb23ae9501c63826a032fd9609a76f06cbe19?pretty=fuller&n=10000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/b61fbbdfbb07406e7e293771f09aace9494bf582

wolenetz@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

ClusterFuzz has detected this issue as fixed in range 574418:574425.

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

Fuzzer: libFuzzer_mediasource_WEBM_VP9_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=505124:505204
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=574418:574425

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

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

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

Probably dupe of  issue 817341 . +jrummell