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

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

Decrease priority and monitor (?) This seems to be an OOM coming from where, I don't know.

ClusterFuzz has detected this issue as fixed in range 557618:557644.

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

Fuzzer: libFuzzer_skia_image_filter_proto_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0539000008f8
Crash State:
  base::OnNoMemorySize
  SkReadBuffer::readByteArrayAsData
  SkPicturePlayback::handleOp
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=533303:533313
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=557618:557644

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

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

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