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

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

Predator could not provide any possible suspects.

From the below CL observing some changes related to file 'skia_image_filter_proto_fuzzer', hence suspecting the same

https://chromium.googlesource.com/chromium/src/+log/94eaf49656b04e5a1215ee8d793217e22111828b..f237d4c82eb90f438e51331dc896b95fa4cadd29?pretty=fuller&n=10000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/868f1e2490e14673494aa5a3a82c591fcf50a0a5

metzman@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

ClusterFuzz has detected this issue as fixed in range 533753:533758.

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

Fuzzer: libFuzzer_skia_image_filter_proto_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  skia_image_filter_proto_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=533300:533313
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=533753:533758

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

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

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