Timeout in javascript_parser_proto_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6133052807053312 Fuzzer: libFuzzer_javascript_parser_proto_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: javascript_parser_proto_fuzzer Sanitizer: undefined (UBSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6133052807053312 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.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.
,
Jan 17 2018
Observing the generated stack trace is related to V8 issue, hence adding appropriate label and marking it as untriaged. Thanks!
,
Jan 17 2018
Marja, this is your fuzzer, right? Even though the test case does not reproduce, the timeout happens frequently (check the statistics in the clusterfuzz report). Maybe you can reproduce this by just running the fuzzer locally for some time? You can then set a breakpoint e.g. in Fuzzer::AlarmCallback and inspect the program state. If it's expected that parsing sometimes takes so long, maybe just reduce the maximum input size.
,
Jan 17 2018
,
Apr 17 2018
We are closing all ooms and timeouts that are unreproducible. We won't be filing such bugs in future. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, Jan 16 2018Labels: Test-Predator-Auto-Components