This issue looks similar to Bug ID -- 738424. So, assigning the same to concern owner who worked on the same file, "icu_util.cc".

@littledan -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

The test case here is an empty HTML file. The failure here seems to be in initializing ICU's data file, which returns an error code and crashes on purpose. There is a comment in the code pointing to this bug, which I don't have access to:

https://bugs.chromium.org/p/chromium/issues/detail?id=445616

I wonder if this is an error in the build process somehow. Anyway, configuring ICU data files is a bit outside my expertise; Jungshik, have you seen issues like this before?

ClusterFuzz has detected this issue as fixed in range 485869:485889.

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

Fuzzer: ksakamoto_woff2_fuzzer
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  result in icu_util.cc
  base::i18n::InitializeICU
  content::ContentMainRunnerImpl::Initialize
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=485825:485869
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=485869:485889

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 5326346661396480 is verified as fixed, so closing issue.

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