Sanitizer CHECK failure in "(("unable to unmap" && 0)) != (0)" (0x0, 0x0) |
||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4980801614905344 Fuzzer: ochang_domfuzzer Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: Sanitizer CHECK failure Crash Address: Crash State: "(("unable to unmap" && 0)) != (0)" (0x0, 0x0) Sanitizer: thread (TSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=399407:399414 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4980801614905344 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Dec 28 2017
ClusterFuzz has detected this issue as fixed in range 526241:526242. Detailed report: https://clusterfuzz.com/testcase?key=4980801614905344 Fuzzer: ochang_domfuzzer Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: Sanitizer CHECK failure Crash Address: Crash State: "(("unable to unmap" && 0)) != (0)" (0x0, 0x0) Sanitizer: thread (TSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=399407:399414 Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=526241:526242 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4980801614905344 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Dec 28 2017
ClusterFuzz testcase 4980801614905344 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||
►
Sign in to add a comment |
||
Comment 1 by kkaluri@chromium.org
, Dec 18 2017Components: Internals
Labels: M-64 Test-Predator-Wrong CF-NeedsTriage