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

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

Unable to identify actual suspect from the predator. By comparing the crash state it looks similar to  bug 793681 , hence cc'ing to same dev for more updates on this issue.

sandersd@ would you mind taking a look in to this issue?

ClusterFuzz has detected this issue as fixed in range 548850:548860.

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

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=543518:543534
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=548850:548860

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

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

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