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 Code Search for the file, "url_canon_icu.cc" assigning to the concern owner who might be related.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/c5698b5c9d00bc9f9e9960995f6def95c714a41d

jshin@ -- Could you please look into the issue.


Thank You.

InitializeICU has to be called before using ICU. Apparently, the fuzzer test in question didn't call Init..ICU.  

I made a CL ( https://chromium-review.googlesource.com/c/chromium/src/+/912355 ), but realized that Jun Choi did it before me for  bug 808412  . 

ClusterFuzz has detected this issue as fixed in range 535905:535914.

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

Fuzzer: libFuzzer_ctap_response_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900006be3
Crash State:
  url::UIDNAWrapper::UIDNAWrapper
  base::LazyInstanceTraitsBase<url::UIDNAWrapper>::New
  url::UIDNAWrapper* base::subtle::GetOrCreateLazyPointer<url::UIDNAWrapper>
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=533878:533899
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=535905:535914

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

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.