Hang in v8_wasm_code_fuzzer |
||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6641451242094592 Fuzzer: libfuzzer_v8_wasm_code_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Hang Crash Address: Crash State: v8_wasm_code_fuzzer Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=427848:428120 Minimized Testcase (0.16 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94OwdXN3iqNKaIpYEY4oDE1RkBnc7UmK4OLM2EA1_73-xfd29s6tq9NprJhO9sNTQlBalEeECaNKYU-fskaPoZKirfpRHnKkDQ80SC8qs_w0VNxqPaVIUPeZcByuUqtKC3dDL0fzdsQCuhvLQPuDKGoo1xLlQ?testcase_id=6641451242094592 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Dec 9 2016
This seems to be grow memory-related, too
,
Dec 13 2016
Is this just a timeout issue? Looks like the test runs fine on my system - it takes a while but completes, and does not hang.
,
Dec 14 2016
The issue seems to be related to asan. Without asan the test case actually finishes fast.
,
Jan 13 2017
ClusterFuzz testcase 6641451242094592 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: mtrofin@chromium.org
Status: Assigned (was: Untriaged)