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

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

ClusterFuzz has detected this issue as fixed in range 555638:555648.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x05390000084a
Crash State:
  sk_abort_no_print
  GrTextureDomain::GrTextureDomain
  GrTextureDomain::GrTextureDomain
  
Sanitizer: address (ASAN)

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

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

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.

A lot of these issues are getting detected as fixed simply because the fuzzer has changed, and uses the starting input for fonts (https://chromium-review.googlesource.com/c/chromium/src/+/1006181).

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

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