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

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

Looks like this is still occurring...to Robert's queue as he has time to look.

ClusterFuzz has detected this issue as fixed in range 555636:555647.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0539000031a4
Crash State:
  to_texture_domain_mode
  SkBlurImageFilterImpl::gpuFilter
  SkBlurImageFilterImpl::onFilterImage
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=527343:527370
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=555636:555647

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

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

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