Out-of-memory in sequence_manager_fuzzer |
||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6625386532962304 Fuzzer: libFuzzer_sequence_manager_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: sequence_manager_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=584148:584149 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6625386532962304 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Aug 20
Automatically adding ccs based on suspected regression changelists: SQM Fuzzer: Add support for multi-threading. by farahcharab@google.com - https://chromium.googlesource.com/chromium/src/+/6a6e23cb7044bf8f79abc09343ce92fc2b1f10ef If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
,
Aug 21
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!
,
Aug 21
@altimin, Dumping the test description generated, all what this test is doing is creating threads as an initial action, so the program is crashing as the fuzzer has a default memory bound set. We probably should limit the number of the threads that can be created, since these use cases are not what we probably want to test.
,
Aug 22
Yeah, limiting the number of threads we can create sounds like a good idea.
,
Oct 9
,
Dec 1
ClusterFuzz testcase 6625386532962304 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 5
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by ClusterFuzz
, Aug 20Labels: Test-Predator-Auto-Components