Out-of-memory in indexed_ruleset_fuzzer |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4622390274031616 Fuzzer: libFuzzer_indexed_ruleset_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: indexed_ruleset_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=563201:563205 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4622390274031616 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jun 5 2018
Note: I think MSAN uses >= 2x the memory as a regular run (due to shadowing all memory allocations). This can be reproduced with a non-MSAN run with -rss_limit_mb=1024.
,
Jul 2
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!
,
Jul 2
Marking available. I don't think this is super high priority but we should probably get to the bottom of it.
,
Oct 31
This seems to be OOM, however it is still happening on M71. Worth to take a look?
,
Nov 1
Still worth taking a look, just haven't had the time to look into it.
,
Dec 1
ClusterFuzz testcase 4622390274031616 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. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ClusterFuzz
, Jun 5 2018Labels: ClusterFuzz-Auto-CC