Issue metadata
Sign in to add a comment
|
Timeout in v8_wasm_fuzzer |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5759407861530624 Fuzzer: libFuzzer_v8_wasm_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: v8_wasm_fuzzer Sanitizer: memory (MSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5759407861530624 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. Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Aug 30 2017
Predator and CL could not provide any possible suspects. Using Code Search for the file, " v8_wasm_fuzzer" assigning to the concern owner. Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/df281a6ec72a6b641b923c1adb0dda1e8feaed2c @ahaas -- Could you please look into the issue, kindly re-assign if this is not related to your changes. Thank You.
,
Sep 11 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Aug 17 2017