Timeout in web_icon_sizes_fuzzer |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5262472935374848 Fuzzer: libFuzzer_web_icon_sizes_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: web_icon_sizes_fuzzer Sanitizer: memory (MSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5262472935374848 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
Unable to perform code search since there is no '.cc' or .cpp' files are available in the stack trace and also no CL file is available to find the suspect, hence adding appropriate label and marking it as untriaged. Thanks!
,
Jan 24 2018
brajkumar@, Blink>Infra doesn't seem appropriate as a fallback label to me. While it has a lot to do with tests (especially LayoutTests), unless there's a suspicion that the infra itself is the cause of the problem, the component for the suspect feature seems better. Going with Blink>HTML>Link since the fuzzer seems to be for an attribute there: https://chromium.googlesource.com/chromium/src/+/7cb9eb91d815ce294fdb7b82ef401c653064695e
,
Jan 26 2018
,
Mar 23 2018
Sorry I no longer work on Chrome except for a very specific part. In WebIconSizesParser, the pointer increments by 1 for every loop iteration, and I don't think the test will timeout for a 1MB input. Verified locally and can't repro. We could limit the maximum input length for WebIconSizesParser. I'm leaning towards closing this bug. Re-assigning to mlamouri@.
,
Apr 17 2018
We are closing all ooms and timeouts that are unreproducible. We won't be filing such bugs in future.
,
Apr 24 2018
ClusterFuzz testcase 5262472935374848 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
,
May 2 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ClusterFuzz
, Jan 16 2018