Out-of-memory in v8_wasm_compile_fuzzer |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4892202357751808 Fuzzer: libFuzzer_v8_wasm_compile_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: v8_wasm_compile_fuzzer Sanitizer: memory (MSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4892202357751808 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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. If the fix resolved the issue, please close the bug by marking as Fixed.
,
Sep 4 2017
,
Sep 6 2017
I think this oom is unrelated to the fuzzer input. There may be a memory leak in the fuzzer though which causes oom's after many fuzzer inputs got executed.
,
Sep 11 2017
Won't fix for now because it cannot be reproduced. |
|||
►
Sign in to add a comment |
|||
Comment 1 by msrchandra@chromium.org
, Sep 4 2017Labels: Test-Predator-Wrong CF-NeedsTriage