New issue
Advanced search Search tips

Issue 680064 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

V8 correctness failure in configs: x64,fullcode:x64,ignition_staging

Project Member Reported by ClusterFuzz, Jan 11 2017

Issue description

Cc: clemensh@chromium.org titzer@chromium.org ahaas@chromium.org
Components: -Blink>JavaScript Blink>JavaScript>WebAssembly
This is just a stack trace difference:

fullcode:
TypeError: Object.prototype.__defineGetter__: Expecting function
ignition_staging (with asm):
TypeError: __v_0.__defineGetter__ is not a function

Is it possible to make those equal or should we suppress it?
Project Member

Comment 2 by bugdroid1@chromium.org, Jan 11 2017

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

commit 733569b70ce6e06e798d79f7843a669c49e7e956
Author: machenbach <machenbach@chromium.org>
Date: Wed Jan 11 11:32:12 2017

[foozzie] Suppress asm stack trace difference

BUG= chromium:680064 
TBR=clemensh@chromium.org, titzer@chromium.org, ahaas@chromium.org
NOTRY=true

Review-Url: https://codereview.chromium.org/2620333002
Cr-Commit-Position: refs/heads/master@{#42217}

[modify] https://crrev.com/733569b70ce6e06e798d79f7843a669c49e7e956/tools/foozzie/v8_suppressions.py

Project Member

Comment 3 by ClusterFuzz, Jan 11 2017

ClusterFuzz has detected this issue as fixed in range 42216:42217.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6220111297118208

Fuzzer: foozzie_js_mutation
Job Type: foozzie_ignition_staging
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,fullcode:x64,ignition_staging
  sources: ac1e8dde
  
Sanitizer: address (ASAN)

Fixed: V8: r42216:42217

Minimized Testcase (0.41 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97Fn4AQPfc9e98WWM703Wa8trepLzAgopnBQ-SRKiZNH-3NLzfvtc1fOTLT7pz3uURjK2z9HoM-awhl4FRsXQK6FB01-C3R5O_1zT-sw5R1cGf9ElU4lAiwaY1KWYG15Zpbe-0cFAEZwGIsYEOSxrQL27PjUbZHxhP37m90nqHgGxUTphiNjR-e1-Q1h2gIspHLz_b5cfTlCTiHbkzEx4-7BltHH4t6udDharT0guj5exA84HeLJFPW-kX1eZwVkrKwe39CiJRC46I0TUS4zGkbxCvzpsrk2F7t-JuCquCp8SiNGR5OONe5sWU2LdZgwVvG7U21lx6mWwFC7F5ezcs_mN5jcflwTyDV_zQWLmY6YCUGnZtrxmD-kLFkeqUkDm5OegIooMooUs78T_ZEGVrdWp_lZw?testcase_id=6220111297118208

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 4 by ClusterFuzz, Jan 11 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 6220111297118208 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Status: Untriaged (was: Verified)
Wrongly closed. This is just suppressed.
Owner: machenb...@chromium.org
Status: Assigned (was: Untriaged)
As discussed, moving to machenbach@ for further triage.
Status: WontFix (was: Assigned)

Sign in to add a comment