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 suspected regression changelists:

Merging gMock, 2 by misterg@google.com - https://chromium.googlesource.com/external/github.com/google/googletest/+/fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

ClusterFuzz has detected this issue as fixed in range 549010:549015.

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

Fuzzer: libFuzzer_mediasource_MP2T_AACSBR_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Bad-cast
Crash Address: 0x7fffe8397288
Crash State:
  Bad-cast to NiceMock<media::MockMediaLog> from media::MockMediaLog
  testing::internal::NiceMockBase<media::MockMediaLog>::NiceMockBase
  testing::NiceMock<media::MockMediaLog>::NiceMock
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=548850:548860
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=549010:549015

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

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

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot