Probably caused by the fact that we can't patch chrome fuzzers.

ClusterFuzz testcase 4642553212960768 appears to be flaky, updating reproducibility label.

Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.

The documentation for reproducing on Windows has been moved to https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md

ClusterFuzz has detected this issue as fixed in range 616918:616922.

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

Fuzzer: libFuzzer_skia_image_decode_fuzzer
Fuzz target binary: skia_image_decode_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

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

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=607281:607292
Fixed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=616918:616922

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 4642553212960768 is verified as fixed, so closing issue as verified.

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