Sanitizer CHECK failure in "((0 && "returned from reporting deadly signal")) != (0)" (0x0, 0x0) |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5109519503589376 Fuzzer: libFuzzer_renderer_fuzzer Fuzz target binary: renderer_fuzzer Job Type: windows_libfuzzer_chrome_asan Platform Id: windows Crash Type: Sanitizer CHECK failure Crash Address: Crash State: "((0 && "returned from reporting deadly signal")) != (0)" (0x0, 0x0) Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=622432:622436 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5109519503589376 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for instructions to reproduce this bug locally.
,
Jan 15
ClusterFuzz testcase 5109519503589376 appears to be flaky, updating reproducibility label.
,
Jan 21
(2 days ago)
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Jan 21
(2 days ago)
Unable to provide possible suspect using Predator, CL and Code Search. Could someone please look into the issue. Thank You... |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Jan 14Labels: ClusterFuzz-Auto-CC