Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Predator and CL could not provide any possible suspects.
Using the code search for the file, “url_idna_icu.cc” assigning to owner concerned from GIT blame.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/8df3a6ffda42808b08501dfdf57edc2464fd94dd

@vasilvv -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 605674:605677.

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

Fuzzer: libFuzzer_lookup_affiliation_response_parser_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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::UIDNAWrapper::UIDNAWrapper
  base::LazyInstanceTraitsBase<url::UIDNAWrapper>::New
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=582875:582879
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=605674:605677

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

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

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