Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

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

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

Assign to hubbe@ who is doing the ffmpeg roll.

Not a security issue, so it can wait until after I come back from vacation.

ClusterFuzz has detected this issue as fixed in range 582251:582262.

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

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  mov_read_packet
  ff_read_packet
  read_frame_internal
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=565361:565375
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=582251:582262

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

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

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