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 OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

This repros for me easily in Linux ToT.  It's just hitting some asserts in GrAAConvexTessellator, such as https://skia.googlesource.com/skia/+/fd6a52cc84364208f65f1ee52644192d6855ab0e/src/gpu/ops/GrAAConvexTessellator.cpp#419.

It looks like if I turn off those asserts, then everything works as normal, so this does not seem to be a security issue.

robertphillips, fmalita: Is this something you want to look at? It seems like maybe a corner failure case of the tessellator.  The fuzzer repros it easily.  If this is not something y'all want to fix, then feel free to close this bug.

ClusterFuzz has detected this issue as fixed in range 568139:568162.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900005460
Crash State:
  sk_abort_no_print
  GrAAConvexTessellator::extractFromPath
  GrAAConvexTessellator::extractFromPath
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=555638:555648
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=568139:568162

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

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.

ClusterFuzz testcase 6754657255555072 is verified as fixed, so closing issue as verified.

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