Timeout in v8_regexp_parser_fuzzer |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6502286601486336 Fuzzer: libFuzzer_v8_regexp_parser_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: v8_regexp_parser_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=397702:398136 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6502286601486336 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 11
,
Nov 12
,
Nov 19
,
Nov 19
Simple d8 repro:
$ time out/debug/d8 --trace-regexp-parser -e 'new RegExp("(|_|){25}_").exec("abc")'
(: (# 25 25 g (^ (| % '_' %))) '_')
(: (# 25 25 g (^ (| % '_' %))) '_')
real 0m2.412s
user 0m2.374s
sys 0m0.044s
,
Dec 1
ClusterFuzz testcase 6502286601486336 appears to be flaky, updating reproducibility label.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 4
,
Dec 22
не понимаю вообще ,по конкретней бы смысл вами написанного сб, 1 дек. 2018 г. в 14:01, ClusterFuzz via monorail < monorail+v2.2757933724@chromium.org>: |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ClusterFuzz
, Nov 10