Timeout in v8_serialized_script_value_fuzzer |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6485983385354240 Fuzzer: libFuzzer_v8_serialized_script_value_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: v8_serialized_script_value_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6485983385354240 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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. If the fix resolved the issue, please close the bug by marking as Fixed.
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 24 2017
For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md. The link referenced in the description is no longer valid.
,
Nov 7 2017
,
Nov 21 2017
The timeout happens during GC. I general I would close timeouts as "won't fix" but I am not familiar with libFuzzer to make the call. mmoroz@, should we close this as "won't fix"? I don't think investigating timeouts is useful.
,
Nov 21 2017
Yeah... for fuzzers targeting V8, most of the timeouts are expected, and there is no need (and probably no way?) to fix those. But some timeouts happen too often and block further progress of the fuzzer. In that case, we are trying to fix the fuzzer in order to avoid triggering those timeouts. Can you take a very quick look at lines 53-101 of https://cs.chromium.org/chromium/src/third_party/WebKit/Source/bindings/core/v8/serialization/SerializedScriptValueFuzzer.cpp?rcl=61bb5cc5255b50e27da51cd2e0a84e1a0d3dacb0&l=53 ? If you have any idea regarding how we can prevent the timeout, please let me know. Otherwise, I'll probably WontFix this as you suggested.
,
Jan 8 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 msrchandra@chromium.org
, Sep 4 2017Components: Blink>JavaScript
Labels: Test-Predator-Correct-CLs
Owner: u...@chromium.org
Status: Assigned (was: Untriaged)