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

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

Predator has provided 5 possible suspects for this issue, since the suspected owners are not chromium users, untriaging this issue and requesting FFMPEG dev team to look into this issue.


Thank You.

ClusterFuzz has detected this issue as fixed in range 523673:523697.

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

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  update_initial_timestamps
  compute_pkt_fields
  parse_packet
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=477380:477461
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=523673:523697

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

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

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