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

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

Marking as WontFix since assertion errors are unimportant in skia and I meant to disable debug builds for this fuzzer.

ClusterFuzz has detected this issue as fixed in range 533741:533755.

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

Fuzzer: libFuzzer_skia_image_filter_proto_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900005082
Crash State:
  sk_abort_no_print
  int SkTo<int, unsigned long>
  int SkTo<int, unsigned long>
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=533293:533313
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=533741:533755

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

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.