Out-of-memory in v8_script_parser_fuzzer |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5336683863343104 Fuzzer: libFuzzer_v8_script_parser_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: v8_script_parser_fuzzer Sanitizer: memory (MSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5336683863343104 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 2 2018
Hm, OOM in the parser fuzzer. Maybe WontFix?
,
Jan 2 2018
Sure, we may WontFix this, given that it happens under MSan which has a large memory overhead. However, we see that sort of crash happening quite often. It would be great if we could find a way to avoid hitting that...
,
Apr 13 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 pnangunoori@chromium.org
, Jan 2 2018Components: Blink>JavaScript
Labels: Test-Predator-Wrong