Out-of-memory in v8_wasm_call_fuzzer |
||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5406459031715840 Fuzzer: libfuzzer_v8_wasm_call_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Out-of-memory Crash Address: Crash State: v8_wasm_call_fuzzer Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=428610:428611 Minimized Testcase (0.02 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96x47CoAxn_YDrHr3GEcuUoXzfy1Xc_lqbvCoheOGP6GsyhffDydIbYiw4Y8mUgT7huejvyZp87_1f3hRkXHIpvZpyQ_D8M9YLd1fkfcb4Mu7h6yylQ_Ax4-vypNDIj6kRT93WE87eF4iIfiiWS61m44Ccktg?testcase_id=5406459031715840 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Jan 7 2017
ClusterFuzz testcase 5406459031715840 is flaky and no longer reproduces, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||
►
Sign in to add a comment |
||
Comment 1 by msrchandra@chromium.org
, Dec 8 2016Labels: Test-Predator-Wrong
Owner: ahaas@chromium.org
Status: Assigned (was: Untriaged)