Timeout in v8_script_parser_fuzzer |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4902300809953280 Fuzzer: libFuzzer_v8_script_parser_fuzzer Fuzz target binary: 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=4902300809953280 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Dec 17
to CF sheriff
,
Dec 17
This is similar to 907738. Another 7kB input that runs into the timeout. Let's reduce the limit to 2kB.
,
Dec 17
Note: Previous such bug ( issue 907738 ) was less than a month ago.
,
Dec 17
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/e7cdc378de877c27f243a2bbf38baf924c6e1312 commit e7cdc378de877c27f243a2bbf38baf924c6e1312 Author: Clemens Hammacher <clemensh@chromium.org> Date: Mon Dec 17 13:39:05 2018 Reduce input size limit of parser fuzzer to 2kB R=mmoroz@chromium.org Bug: chromium:911644 Change-Id: Icc42e5ace80ea816925c95e2ea330b484b68e7cf Reviewed-on: https://chromium-review.googlesource.com/c/1379878 Reviewed-by: Marja Hölttä <marja@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#58280} [modify] https://crrev.com/e7cdc378de877c27f243a2bbf38baf924c6e1312/test/fuzzer/parser.cc
,
Dec 18
ClusterFuzz has detected this issue as fixed in range 617197:617205. Detailed report: https://clusterfuzz.com/testcase?key=4902300809953280 Fuzzer: libFuzzer_v8_script_parser_fuzzer Fuzz target binary: 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 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=617197:617205 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4902300809953280 See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Dec 18
ClusterFuzz testcase 4902300809953280 is verified as fixed, so closing issue as verified. 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
, Dec 5