Timeout in v8_wasm_code_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5162984113176576 Fuzzer: libFuzzer_v8_wasm_code_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: v8_wasm_code_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=529682:529689 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5162984113176576 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Feb 14 2018
,
Feb 14 2018
Hello, this CL should only have effect on platforms using constant pool. Apparently, ppc is the only platform enabling constant pool by default. And I have no permission to see the detailed report.
,
Feb 16 2018
,
Feb 17 2018
The test case only takes 0.2 seconds to complete on my machine, even though it executes a number of grow_memory instructions. Cannot test with msan, because it's still not supported on rodete. Marking WontFix for now.
,
Feb 24 2018
ClusterFuzz testcase 5162984113176576 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
,
Mar 5 2018
,
Mar 8 2018
Issue 819581 has been merged into this issue.
,
Mar 12 2018
Issue 820857 has been merged into this issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, Feb 13 2018Labels: Test-Predator-Auto-CC