New issue
Advanced search Search tips

Issue 725905 link

Starred by 1 user
Status: WontFix
Owner:
ahaas@chromium.org
Closed: Jun 2017
Cc:
clemensh@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Timeout in v8_wasm_fuzzer

Project Member Reported by ClusterFuzz, May 24 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5016805826625536

Fuzzer: libfuzzer_v8_wasm_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  v8_wasm_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=449266:449283

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


Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, May 24 2017

Components: Blink>JavaScript
Labels: Test-Predator-Wrong M-59

Comment 2 by ishell@chromium.org, May 26 2017

Cc: clemensh@chromium.org
Owner: ahaas@chromium.org
Status: Assigned (was: Untriaged)
Andreas, please take a look why does the wasm fuzzer timeout.

Comment 3 by ahaas@chromium.org, May 29 2017

Labels: -Pri-1 Pri-2
The generated test case contains an infinite loop. I have to think about how I can fix that.
Project Member

Comment 4 by ClusterFuzz, Jun 28 2017

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5016805826625536 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