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 find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from Dev team to look in to this issue.

Thanks!

Null reads are P2.

The regression range is from December and the crash seems to only affect Beta and Stable according to ClusterFuzz. Probably a WontFix as we are not shipping with Beta/Stable.

ClusterFuzz testcase 5705366663593984 appears to be flaky, updating reproducibility label.

ClusterFuzz has detected this issue as fixed in range 572492:572493.

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

Fuzzer: inferno_canvas_wrecker
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
  media::VideoResourceUpdater::CreateExternalResourcesFromVideoFrame
  blink::VideoFrameResourceProvider::AppendQuads
  blink::VideoFrameSubmitter::SubmitFrame
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=572492:572493

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

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

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