ClusterFuzz has detected this issue as fixed in range 609442:609458.

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

Fuzzer: libFuzzer_skia_region_set_path_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  skia_region_set_path_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=609442:609458

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

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.

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