New issue
Advanced search Search tips

Issue 749838 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug

Blocking:
issue 584819



Sign in to add a comment

Timeout in v8_wasm_async_fuzzer

Project Member Reported by ClusterFuzz, Jul 27 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5004403261308928

Fuzzer: libFuzzer_v8_wasm_async_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  v8_wasm_async_fuzzer
  
Sanitizer: address (ASAN)

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5004403261308928


Issue manually filed by: mmoroz

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 

Comment 1 by mmoroz@chromium.org, Jul 27 2017

Blocking: 584819
Cc: mmoroz@chromium.org
Components: Blink>JavaScript>WebAssembly
Owner: ahaas@chromium.org
Andreas, this timeout issue is happening in 70+% of fuzzer runs: https://clusterfuzz.com/v2/performance-report/libFuzzer_v8_wasm_async_fuzzer/libfuzzer_chrome_asan/latest

I wonder if you have any clue how to fix or at least to avoid hitting it :)
Status: Assigned (was: Untriaged)

Comment 3 by ahaas@chromium.org, Jul 31 2017

Status: Started (was: Assigned)
Project Member

Comment 4 by bugdroid1@chromium.org, Aug 3 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/859ee8443d85274c5db6bc27126713e82c609a9b

commit 859ee8443d85274c5db6bc27126713e82c609a9b
Author: Andreas Haas <ahaas@chromium.org>
Date: Thu Aug 03 08:45:58 2017

[wasm] Move ScheduledErrorThrower to wasm-api.h

The ScheduledErrorThrower is also needed in the wasm-async fuzzer so I
moved the implementation from wasm-js.cc to wasm-api.[h|cc].

R=clemensh@chromium.org

Bug:  chromium:749838 
Change-Id: I49d7438d1ec0281285ce0c64ba462c22001be08e
Reviewed-on: https://chromium-review.googlesource.com/591447
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Reviewed-by: Clemens Hammacher <clemensh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#47112}
[modify] https://crrev.com/859ee8443d85274c5db6bc27126713e82c609a9b/BUILD.gn
[modify] https://crrev.com/859ee8443d85274c5db6bc27126713e82c609a9b/src/v8.gyp
[add] https://crrev.com/859ee8443d85274c5db6bc27126713e82c609a9b/src/wasm/wasm-api.cc
[add] https://crrev.com/859ee8443d85274c5db6bc27126713e82c609a9b/src/wasm/wasm-api.h
[modify] https://crrev.com/859ee8443d85274c5db6bc27126713e82c609a9b/src/wasm/wasm-js.cc
[modify] https://crrev.com/859ee8443d85274c5db6bc27126713e82c609a9b/test/fuzzer/wasm-async.cc
[add] https://crrev.com/859ee8443d85274c5db6bc27126713e82c609a9b/test/fuzzer/wasm_async/valid.wasm

Project Member

Comment 5 by ClusterFuzz, Sep 2 2017

Status: WontFix (was: Started)
ClusterFuzz testcase 5004403261308928 is flaky and no longer reproduces, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Comment 6 by mmoroz@chromium.org, Sep 30 2017

Labels: ClusterFuzz-Wrong
Status: Fixed (was: WontFix)
Thanks Andreas for the fix, it worked well. Issue is Fixed.

Sign in to add a comment