Timeout in icu_break_iterator_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5660168141144064 Fuzzer: libFuzzer_icu_break_iterator_fuzzer Job Type: windows_libfuzzer_chrome_asan Platform Id: windows Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: icu_break_iterator_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5660168141144064 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 26
mmoroz@, just wondering do you have any inputs here?
,
Oct 26
This is probably a bug in ICU. Or we might want to update the fuzz target to reject inputs which are too long. Assigning to jshin@ who's ICU owner as per https://cs.chromium.org/chromium/src/third_party/icu/OWNERS And CC'ing metzman@ just in case this is something windows specific.
,
Oct 29
This only happens on Windows? Argh.. it'd be hard to debug because I don't have a physical Windows machine. Let me try on Linux with the test case.
,
Oct 29
Doesn't look like it has the same problem on Linux (see https://clusterfuzz.com/v2/testcase-detail/5659580611428352?noredirect=1). I'll try to take a look and figure out what is going on, on Win.
,
Nov 30
ClusterFuzz testcase 5660168141144064 appears to be flaky, updating reproducibility label.
,
Nov 30
ClusterFuzz testcase 5660168141144064 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 kkaluri@chromium.org
, Oct 23Labels: Test-Predator-Wrong CF-NeedsTriage M-70