Predator and CL did not provide any possible suspects.
Using Code Search for the file, "icu_util.cc" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/v8/v8.git/+/2f8cae53f8e29980337ba5c111a05ac66bb882cc

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

ClusterFuzz has detected this issue as fixed in range 483641:483653.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: windows_asan_chrome
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_chrome&range=483625:483641
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=483641:483653

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


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 4665917056483328 is verified as fixed, so closing issue.

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