Out-of-memory in safe_browsing_hfs_fuzzer |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5715868045279232 Fuzzer: libFuzzer_safe_browsing_hfs_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: safe_browsing_hfs_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=509376:509426 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5715868045279232 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 10
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!
,
Oct 11
rsesek@, it is OOM, really worth to investigate?
,
Oct 11
,
Oct 11
Nah.
,
Oct 18
ClusterFuzz testcase 5715868045279232 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
,
Oct 18
,
Dec 1
ClusterFuzz testcase 5715868045279232 appears to be flaky, updating reproducibility label. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ClusterFuzz
, Oct 9Labels: ClusterFuzz-Auto-CC