Out-of-memory in blink_http_parsers_fuzzer |
||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5679942878363648 Fuzzer: libFuzzer_blink_http_parsers_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: blink_http_parsers_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=603675:604734 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5679942878363648 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 18
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Nov 20
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 21
,
Dec 1
ClusterFuzz testcase 5679942878363648 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 4
metzman@, This seems to be OOM and not very sure if it's worth to take a look?
,
Dec 6
,
Dec 11
ClusterFuzz testcase 5679942878363648 appears to be flaky, updating reproducibility label.
,
Dec 11
Quarantine size change has probable made this issue unreproducible (intentionally). |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by ClusterFuzz
, Nov 18