Out-of-memory in merkle_integrity_source_stream_fuzzer |
|||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5165939924140032 Fuzzer: libFuzzer_merkle_integrity_source_stream_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: merkle_integrity_source_stream_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=585308:585313 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5165939924140032 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 8
Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue. Thanks!
,
Nov 8
,
Nov 12
Actually, looking at the stack trace (didn't look at it earlier), this issue appears to be external to the fuzzer, unless there was a leak from previous runs and the fuzzer infrastructure's being blamed. +inferno, thoughts?
,
Nov 20
,
Dec 1
ClusterFuzz testcase 5165939924140032 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 3
inferno: Could you take a look at this? The stack trace suggests that the OOM is happening in libFuzzer infrastructure rather than the fuzzer itself. Thanks!
,
Jan 4
ClusterFuzz testcase 5165939924140032 appears to be flaky, updating reproducibility label.
,
Jan 9
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. Comment 8 by davidben
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by ClusterFuzz
, Nov 8Labels: ClusterFuzz-Auto-CC