Timeout in xml_parser_fuzzer |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5680376509628416 Fuzzer: libFuzzer_xml_parser_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: xml_parser_fuzzer Sanitizer: memory (MSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5680376509628416 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.
,
Mar 28 2018
,
Apr 12 2018
Other assigned bug cover this, I believe.
,
Apr 16 2018
Issue 833096 has been merged into this issue.
,
Apr 19 2018
ClusterFuzz testcase 6514275397664768 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. |
||||
►
Sign in to add a comment |
||||
Comment 1 by brajkumar@chromium.org
, Feb 6 2018Components: Blink>XML
Labels: -Pri-1 Test-Predator-Wrong CF-NeedsTriage Pri-2