CHECK failure: false. failed to open UTS46 data with error: 4. If you see this error message in |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4577480429273088 Fuzzer: libFuzzer_csv_reader_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: 4. If you see this error message in url::UIDNAWrapper::UIDNAWrapper base::LazyInstanceTraitsBase<url::UIDNAWrapper>::New Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=515509:515520 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4577480429273088 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Dec 20 2017
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Dec 20 2017
Predator and CL could not provide any possible suspects. Using the code search for the file, “url_canon_icu.cc” assigning to concern owner from GIT blame. Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/86b18513e6a146a530d974186aefddd1611cb9d2 @ellyjones -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes. Thank You.
,
Jan 2 2018
As the error message for the CHECK says, this is issue 778929 . |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Dec 20 2017