New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 709449 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Apr 2017
Cc:
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, Apr 7 2017

Issue description

Cc: mart...@martijnc.be a...@chromium.org ellyjo...@chromium.org csharrison@chromium.org aizatsky@chromium.org
Labels: Test-Predator-Wrong M-59
Predator and regression range did not given any culprit CL.
Could someone please take a look?
Thank you.

Comment 3 by a...@chromium.org, Apr 8 2017

Owner: dominicc@chromium.org
Status: Assigned (was: Untriaged)
dominicc:

Your new fuzzer fails because you fail to have the correct ICU dependency.
Project Member

Comment 4 by ClusterFuzz, Apr 8 2017

ClusterFuzz has detected this issue as fixed in range 462804:462820.

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

Fuzzer: libfuzzer_template_url_parser_fuzzer
Job Type: libfuzzer_chrome_msan
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: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=462791:462804
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=462804:462820

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94xwUypMkdS50ec8C-jeulbAFscIx5kiDesrfG26WNMbnRO8pQlTYgy6PF5dKNA2jDihBOfHETqi1kTLcnHLWGV865nFJclD1ITzomxa7fdwd2WjEy6nJRftCYdo_NRxoVNym5cs0emYQAtDDauEF7QN7mILf7Y4TUV_o_bajPoabcTCY02VMUm7Ikhqwd5h7-rIykikawltlbswE2N56BKjCbe9DgtjwjdO0Axu2o9hgaXvl86TzKX04fn8BTqP7t_9xt4gwPiOCSsOjQAXjqAitVZdhbPUUjRK8FhaX6fdq51XK0H-orOQfJGuoxjj_QkZ9Dvl_CrcwZeSl74gNz-hMRPlfz5VdNFC0OWQ0sO99bOwWo?testcase_id=6061863990460416


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 5 by ClusterFuzz, Apr 8 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 6061863990460416 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Hmm, OK. Is that a problem with the fuzzer build file or the component I'm fuzzing? Can you point to something with the correct dependency I can crib from?
Usually this happens due to not initializing ICU. See BlinkFuzzerTestSupport.cpp and net/base/fuzzer_test_support.cc for some things that usually need initializing.
Status: Started (was: Verified)
Reopening this to add the ICU initialization.
Status: Fixed (was: Started)
OK I believe this should be good now. Thank you for the pointers.

Sign in to add a comment