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

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

Just looked into this code with Robert. It appears that the blur paint filter serialization code may need a look, and a number of these fuzzer bugs are erroneously sitting in our court vs paint ops, so sending over...

ClusterFuzz has detected this issue as fixed in range 555645:555651.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000984
Crash State:
  sk_abort_no_print
  to_texture_domain_mode
  SkBlurImageFilterImpl::gpuFilter
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=527364:527373
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=555645:555651

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

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

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