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 is an assert that a bisector vector is not close to zero.  However, I think it'd always be possible to generate a bisector that hits this case.  Removing the assert results in no other crashes, so this seems spurious.

ClusterFuzz has detected this issue as fixed in range 574746:574747.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900004ec1
Crash State:
  sk_abort_no_print
  GrAAConvexTessellator::Ring::computeBisectors
  GrAAConvexTessellator::Ring::computeBisectors
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=558574:558581
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=574746:574747

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

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.