Indirect-leak in xmlNewDocElementContent |
|||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5471909975425024 Fuzzer: libfuzzer_libxml_xml_read_memory_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Indirect-leak Crash Address: Crash State: xmlNewDocElementContent xmlParseElementMixedContentDecl xmlParseElementContentDecl Sanitizer: address (ASAN) Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=414961:414962 Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95ZXFVbknRDim6QEjiLfmQAom_U7YJRi-pid3E2BRkoFmMpLUb-bA4tgAOMpZRHQRa5mw_zpCaxiebUdTZoE3IlIqAMTEwToOHrdE3mXceXur_sSwP5z_uZw5pIFWgHVVs76bEpEuSxhSuC_tmlF_ZD-K3DhKuEhFupJg9PDPS7DXrrv1W8EEW_8y4HLTDBh70MCR9-SIy3MGvKwW1zCJYCtafSonuXkNycYR_bX7U2fkPsAtKdWKQ14DKCj11mWyHEBJO4-njR-ThTTuqB2puhsBHS7NdFK_4jjHl_VXaN829wGyz9iLblOlpLps7RTwonjA6uH2Vq3vc5RM9JPPemEUw4fo0TjQzOcNEekO2omBrQhKL3sBiE4o1XpF98dYEn4amZTyBC2ZmlSfKIU6Iyxrw8pQ?testcase_id=5471909975425024 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Feb 7 2017
,
Jun 21 2017
ClusterFuzz has detected this issue as fixed in range 480710:480765. Detailed report: https://clusterfuzz.com/testcase?key=5471909975425024 Fuzzer: libFuzzer_libxml_xml_read_memory_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Indirect-leak Crash Address: Crash State: xmlNewDocElementContent xmlParseElementMixedContentDecl xmlParseElementContentDecl Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=414961:414962 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=480710:480765 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5471909975425024 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jun 21 2017
ClusterFuzz testcase 5471909975425024 is verified as fixed, 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 nyerramilli@chromium.org
, Feb 7 2017Labels: Test-Predator-Wrong-CLs M-58
Owner: scottmg@chromium.org
Status: Assigned (was: Untriaged)