Hang in libxml_xml_read_memory_fuzzer |
|||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5130104058675200 Fuzzer: libfuzzer_libxml_xml_read_memory_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Hang Crash Address: Crash State: libxml_xml_read_memory_fuzzer Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=395689:395794 Minimized Testcase (0.72 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95QpeFK8kk7Bc2-3FHPd4OGTOMiIQawgXPLq0aipAsM-urjpw-85U3nscLqSTDoSu-jzwon6HBbLl-gzLWJdaoVa5jwFyRiMx3Q_annGFXrgoo8bQc0gZTxPwfio-yEs96PqzdZuRCsHYbHG1TAaCvqcq_nDw?testcase_id=5130104058675200 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 23 2017
Assigning to concern owner who might be related to similar kind of Fuzzers. @mmoroz -- Could you please look into the issue, kindly re-assign if this is not related to you or your changes. Thank You.
,
Jan 23 2017
,
Mar 22 2017
,
Jun 7 2017
ClusterFuzz testcase 5130104058675200 is flaky and no longer reproduces, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ajha@chromium.org
, Nov 22 2016