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 527331:527341.

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

Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  sk_realloc_throw
  SkAutoTMalloc<unsigned char>::realloc
  SkTextBlobBuilder::reserve
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=527050:527055
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=527331:527341

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

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 6637269418246144 is verified as fixed, so closing issue as verified.

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

Fixed by vmpstr's leak fix.