Out-of-memory in css_parser_proto_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4728368921837568 Fuzzer: libFuzzer_css_parser_proto_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: css_parser_proto_fuzzer Sanitizer: memory (MSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4728368921837568 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
,
Jan 16 2018
Unable to perform code search since there is no '.cc' or .cpp' files are available in the stack trace and also no CL file is available to find the suspect, hence adding appropriate label and marking it as untriaged. Thanks!
,
Jan 17 2018
Hi metzman, I think you were working on the css_parser_proto_fuzzer? It'd be interesting to see if this is the same issue as https://bugs.chromium.org/p/chromium/issues/detail?id=772612
,
Jan 31 2018
,
Apr 17 2018
We are closing all ooms and timeouts that are unreproducible. We won't be filing such bugs in future. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, Jan 15 2018