New issue
Advanced search Search tips

Issue 789568 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 778929
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: false. failed to open UTS46 data with error: 4 in url_canon_icu.cc

Project Member Reported by ClusterFuzz, Nov 29 2017

Issue description

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

Fuzzer: libFuzzer_payment_method_manifest_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false. failed to open UTS46 data with error: 4 in url_canon_icu.cc
  url::UIDNAWrapper::UIDNAWrapper
  base::LazyInstanceTraitsBase<>::New
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=502004:502042

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Cc: kkaluri@chromium.org
Components: Internals>Core
Labels: M-63 Test-Predator-Wrong-CLs
Owner: ellyjo...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using the code search for the file, “url_canon_icu.cc” assigning to concern owner.

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...
Mergedinto: 778929
Status: Duplicate (was: Assigned)
How do I file bugs against ClusterFuzz? This is another duplicate of  issue 778929 . ClusterFuzz's test setup is still broken and as long as it stays broken this check will keep failing.
Cc: mmoroz@chromium.org
mmoroz@, can you please respond to c#2?

Comment 4 by mmoroz@chromium.org, Nov 30 2017

ellyjones@, please file a bug with Tools>Stability>ClusterFuzz component, or just shoot an email to clusterfuzz-dev@.
mmoroz@: filed as issue 790991, thanks :)

Sign in to add a comment