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

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

geofflang: I know this is from a while ago, but could have this regressed with https://chromium.googlesource.com/chromium/src/+/1d0ecd382887571a8bb00e1289d1b67eaa6a1396 ? The regression range is also large.

There is no way that this crash was caused by ANGLE.  CCing Chris Cameron who may know a good owner for fixing this.

ccameron@, could please take a look and / or help to find an owner.

This is an unactionable GL driver bug

ClusterFuzz has detected this issue as fixed in range 588975:588981.

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

Fuzzer: inferno_canvas_wrecker
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: UNKNOWN READ
Crash Address: 0x00023e58a650
Crash State:
  glvmRasterOpRead
  glvmInterpretFPTransformFour
  gldLLVMFPTransform
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=389555:389622
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=588975:588981

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

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 5161759124750336 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