Null-dereference READ in base::internal::LockImpl::Lock |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5579798158770176 Fuzzer: libFuzzer_sequence_manager_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: base::internal::LockImpl::Lock base::Lock::Acquire base::AutoLock::AutoLock Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=586754:586756 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5579798158770176 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Sep 25
Automatically adding ccs based on suspected regression changelists: SQM Fuzzer: Add support for cross-thread posting. by farahcharab@google.com - https://chromium.googlesource.com/chromium/src/+/f67097b4acac3a85de15f259ee38295da301802e If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
,
Sep 26
Predator has provided the 1 possible suspect, hence assigning to author. Suspect CL : https://chromium.googlesource.com/chromium/src/+/f67097b4acac3a85de15f259ee38295da301802e farahcharab@ Could you please look into it.
,
Dec 1
ClusterFuzz testcase 5579798158770176 appears to be flaky, updating reproducibility label.
,
Dec 1
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.
,
Dec 1
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.
,
Dec 6
ClusterFuzz has detected this issue as fixed in range 614320:614321. Detailed report: https://clusterfuzz.com/testcase?key=5579798158770176 Fuzzer: libFuzzer_sequence_manager_fuzzer Fuzz target binary: sequence_manager_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: base::internal::LockImpl::Lock base::Lock::Acquire base::AutoLock::AutoLock Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=586754:586756 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=614320:614321 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5579798158770176 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Dec 6
ClusterFuzz testcase 5579798158770176 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 ClusterFuzz
, Sep 25Labels: Test-Predator-Auto-Components