With reference to the  Issue 882656 , assigning it to the vasilvv@ 

ClusterFuzz testcase 4957937325572096 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.

ClusterFuzz has detected this issue as fixed in range 613409:613412.

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

Fuzzer: libFuzzer_gpu_fuzzer
Fuzz target binary: gpu_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false. failed to open UTS46 data with error: U_FILE_ACCESS_ERROR. If you see thi
  url::IDNToASCII
  url::DoIDNHost
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=606029:606031
Fixed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=613409:613412

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

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 4957937325572096 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