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

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

PaintOpBuffer fuzzer asserts are WontFix.

ClusterFuzz testcase 4596968440725504 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 529162:529166.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900007c65
Crash State:
  sk_abort_no_print
  validate_edges_for_y
  validate_edges_for_y
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=496919:496954
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=529162:529166

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

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.