ClusterFuzz has detected this issue as fixed in range 606943:606976.

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

Fuzzer: libFuzzer_skia_image_decode_incremental_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_incremental_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=606937:606939
Fixed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=606943:606976

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing_on_windows.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 6221378929557504 is verified as fixed, so closing issue as verified.

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

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