New issue
Advanced search Search tips

Issue 718123 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

V8 correctness failure in configs: x64,ignition:ia32,ignition

Project Member Reported by ClusterFuzz, May 3 2017

Issue description

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:ia32,ignition
  sources: 805
  
Sanitizer: address (ASAN)

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


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Components: -Blink>JavaScript Blink>JavaScript>Interpreter
Owner: rmcilroy@chromium.org
Status: Assigned (was: Untriaged)
different results for ia32 vs x64 on mjsunit/es6/math-hypot.js with ignition
Cc: jochen@chromium.org rmcilroy@chromium.org
Owner: machenb...@chromium.org
Hmm, not sure about this. Looks more like stable vs. unstable sorting. Will try to repro.
Cc: mvstan...@chromium.org mstarzinger@chromium.org
Labels: -Pri-1 Pri-2
Owner: ----
Status: Available (was: Assigned)
Reduced the test case. @mstarzinger,mvstanton: This is dependent on setting configurable: false of the first element. Is this triggering different sorting algorithms? If that's the case and that's expected then the symptom is just a duplicate of  issue 707550 .

a = [13, 6];
Object.defineProperty(a, '0', { configurable: false });
a.sort(function() {});
print(a);

// Output:
### Start of configuration x64,ignition:
13,6

### End of configuration x64,ignition
#
### Start of configuration ia32,ignition:
6,13

### End of configuration ia32,ignition
Project Member

Comment 4 by ClusterFuzz, May 16 2017

ClusterFuzz has detected this issue as fixed in range 45316:45317.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:ia32,ignition
  sources: 805
  
Sanitizer: address (ASAN)

Fixed: V8: 45316:45317

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


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 5 by ClusterFuzz, May 16 2017

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Cc: -jochen@chromium.org -rmcilroy@chromium.org
Labels: ClusterFuzz-Wrong
Owner: machenb...@chromium.org
Status: Assigned (was: Verified)
Clusterfuzz still claims fixed. Will try to repro locally.
Labels: -ClusterFuzz-Wrong
We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.

Sign in to add a comment