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:

Fix media log for complexity based buffering to use milliseconds. by dalecurtis@chromium.org - https://chromium.googlesource.com/chromium/src/+/f629599a409425e9543f7888d4abfc543b035448

Set color space and HDR metadata in android.media.MediaFormat by sandv@chromium.org - https://chromium.googlesource.com/chromium/src/+/ee50dff9800ed3ea00f2227204ed84c4c6953be4

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

ClusterFuzz has detected this issue as fixed in range 521445:521495.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::WebScopedVirtualTimePauser::PauseVirtualTime
  media::MultiBuffer::AddReader
  media::MultiBufferReader::UpdateInternalState
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=521161:521182
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=521445:521495

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

See https://github.com/google/clusterfuzz-tools 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 5856786702925824 is verified as fixed, so closing issue as verified.

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