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

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

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

Likely caused by https://chromium-review.googlesource.com/c/chromium/src/+/561921

ClusterFuzz has detected this issue as fixed in range 589552:589567.

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

Fuzzer: inferno_twister
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: UNKNOWN WRITE
Crash Address: 0x000147d38000
Crash State:
  cc::RestoreOp::Serialize
  cc::PaintOp::Serialize
  gpu::raster::PaintOpSerializer::Serialize
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=585071:585171
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=589552:589567

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

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 5742118707134464 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 requires manual review: M70 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: benmason@(Android), kariahda@(iOS), geohsu@(ChromeOS), abdulsyed@(Desktop)

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

Hi enne - mind taking a look at the fixed range (https://clusterfuzz.com/v2/revisions?job=mac_asan_chrome&range=589552%3A589567&noredirect=1) and see if there's a fix there we should merge to M70?

There is nothing even remotely obvious in that changelist, unfortunately.  I even looked through the Skia changes just in case.  Thanks for asking though; that's a really good thought.

Thanks for looking!

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