Timeout in icu_break_iterator_utf32_fuzzer |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5084924045688832 Fuzzer: libFuzzer_icu_break_iterator_utf32_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: icu_break_iterator_utf32_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5084924045688832 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information. Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
,
Oct 23 2017
,
Oct 23 2017
Assigning to jshin@, ICU owner.
,
Oct 23 2017
Hmm.... ICU is going to be updated to 60 soon. And, there's a major change in BreakIterator in ICU 60. Hope that this would not happen with the new RBBI code in ICU 60. OTOH, we have to deal with existing Chrome releases (M62, M63)... argh...
,
Oct 23 2017
oh... if this crash only happens with UTF-32 input, we may not have to worry about exiting Chrome releases because Chrome/Blink does not use UTF-32 input (afaik).
,
Oct 23 2017
> if this crash only happens with UTF-32 input The test input is not valid UTF-32 (either LE or BE) because it has code points beyond plane 16. So, in Chrome/v8, this kind of invalid input will not reach ICU. Among other reasons, Chrome/Blink does not support UTF-32 input any more. I'll downgrade to Pri-3 once I'm sure.
,
Oct 24 2017
For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md. The link referenced in the description is no longer valid.
,
Nov 20 2017
ClusterFuzz testcase 5084924045688832 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by pnangunoori@chromium.org
, Oct 23 2017Labels: Test-Predator-Wrong
Owner: mmoroz@chromium.org
Status: Available (was: Untriaged)