New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 811758 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in v8_wasm_code_fuzzer

Project Member Reported by ClusterFuzz, Feb 13 2018

Issue description

Detailed 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.
 
Project Member

Comment 1 by ClusterFuzz, Feb 13 2018

Cc: j...@ca.ibm.com
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Change RelocInfo to use constant_pool_ variable instread of host_ by jyan@ca.ibm.com - https://chromium.googlesource.com/v8/v8/+/163fe17c76fcbd6783f947b2c599f429e03f7c07

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
Components: Blink>JavaScript
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.
Project Member

Comment 4 by ClusterFuzz, Feb 16 2018

Labels: OS-Mac
Cc: ahaas@chromium.org
Owner: clemensh@chromium.org
Status: WontFix (was: Untriaged)
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.
Project Member

Comment 6 by ClusterFuzz, Feb 24 2018

Labels: Needs-Feedback
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.
Cc: brajkumar@chromium.org
 Issue 818499  has been merged into this issue.
 Issue 819581  has been merged into this issue.
 Issue 820857  has been merged into this issue.

Sign in to add a comment