lookup_affiliation_response_parser_fuzzer crashes very frequently |
||
Issue descriptionhttps://clusterfuzz.com/v2/performance-report/libFuzzer_lookup_affiliation_response_parser_fuzzer/libfuzzer_chrome_asan/2018-10-30 Crashing on almost every single run with: [1030/090621.992925:FATAL:url_idna_icu.cc(50)] Check failed: false. failed to open UTS46 data with error: U_FILE_ACCESS_ERROR. If you see this error message in a test environment your test environment likely lacks the required data tables for libicu. See https://crbug.com/778929 .
,
Nov 6
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/54b589358cd6d123b41bcde3892ee03a037604ec commit 54b589358cd6d123b41bcde3892ee03a037604ec Author: Christopher Thompson <cthomp@chromium.org> Date: Tue Nov 06 15:13:39 2018 Add IcuEnvironment setup to affiliation parser fuzzer The lookup_affiliation_response_parser_fuzzer frequently crashes due to being unable to open the libicu test environment data tables. This adds IcuEnvironment setup code to the fuzz target to properly set up libicu before fuzzing. This follows the approach taken in https://crbug.com/754996#c15 Bug: 900811 Change-Id: Iebb7a7b7e8fac6ae6a089da1d51d2d85846b9967 Reviewed-on: https://chromium-review.googlesource.com/c/1318735 Reviewed-by: Abhishek Arya <inferno@chromium.org> Reviewed-by: Vaclav Brozek <vabr@chromium.org> Reviewed-by: Max Moroz <mmoroz@chromium.org> Commit-Queue: Abhishek Arya <inferno@chromium.org> Cr-Commit-Position: refs/heads/master@{#605675} [modify] https://crrev.com/54b589358cd6d123b41bcde3892ee03a037604ec/components/password_manager/core/browser/BUILD.gn [modify] https://crrev.com/54b589358cd6d123b41bcde3892ee03a037604ec/components/password_manager/core/browser/android_affiliation/lookup_affiliation_response_parser_fuzzer.cc
,
Nov 7
fix worked. https://clusterfuzz.com/v2/fuzzer-stats/by-time/date-start/2018-10-31/date-end/2018-11-06/fuzzer/libFuzzer_lookup_affiliation_response_parser_fuzzer I wonder if there are similar issues with some other targets. maybe sort by fuzzing time percent on https://clusterfuzz.com/v2/fuzzer-stats/by-fuzzer/date-start/2018-10-31/date-end/2018-11-06/fuzzer/libFuzzer/job/libfuzzer_chrome_asan
,
Nov 7
I've checked through the logs for all fuzzers for 2018-11-06, and lookup_affiliation_response_parser_fuzzer appears to be the only one that was tripping this CHECK, so I don't think there is anything else to be done here (although there may be similar-but-not-the-same setup issues in other fuzzers). |
||
►
Sign in to add a comment |
||
Comment 1 by cthomp@chromium.org
, Nov 5Status: Started (was: Available)