Sanitizer CHECK failure in ((0)) != (0) (0, 0) |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4515898340933632 Fuzzer: libFuzzer_pdf_codec_gif_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Sanitizer CHECK failure Crash Address: Crash State: ((0)) != (0) (0, 0) Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=501422:501484 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4515898340933632 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Sep 13 2017
These allocator failures produce very poor report. Could we add a description of the failure and a stack trace?
,
Sep 14 2017
ClusterFuzz testcase 4515898340933632 is flaky and no longer crashes, 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 msrchandra@chromium.org
, Sep 13 2017Labels: M-63 CF-NeedsTriage Test-Predator-Wrong