Timeout in v8_script_parser_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4604695928373248 Fuzzer: libFuzzer_v8_script_parser_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: v8_script_parser_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=607560:607561 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4604695928373248 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 26
Hm, I can't measure any difference locally between 607560 and 607561. On a release build, the test case executes in ~0.3 seconds. Note that clusterfuzz used a debug asan bot. Should we just reduce the allowed test case size? It's 8kB currently. Would we loose any coverage by reducing it to, say, 1kB?
,
Nov 26
Afaics this is not my fuzzer... assigning to fuzzer folks
,
Nov 26
The fuzzer seems to be quite old and didn't find any failures recently. Since we have more specialized fuzzers, we could just remove it.
,
Nov 26
Actually, this fuzz target is reporting some valid stuff: https://bugs.chromium.org/p/chromium/issues/list?can=1&q=description%3AlibFuzzer_v8_script_parser_fuzzer%2Cafl_v8_script_parser_fuzzer&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids
,
Nov 26
This particular timeout is probably WontFix, as (A) it doesn't happen too often (just 6 times over the past 21 days) and (B) it's in the debug build. If it re-occurs more frequently, we can try enforcing a shorter input (e.g. reproducer for this one is 7KB).
,
Dec 1
ClusterFuzz testcase 4604695928373248 appears to be flaky, updating reproducibility label. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by kkaluri@chromium.org
, Nov 22