New issue
Advanced search Search tips

Issue 694088 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

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

Project Member Reported by ClusterFuzz, Feb 20 2017

Issue description

Cc: bmeu...@chromium.org mstarzinger@chromium.org
Owner: jarin@chromium.org
Status: Assigned (was: Untriaged)
// PTAL. Only repros with --always-opt. Seems introduced by:
// https://chromium.googlesource.com/v8/v8/+/36ed494784706c3c573c7d5fdd61d93a33dcb91a

var buffer = new ArrayBuffer(4);
var i16 = new Int16Array(buffer);
var i32 = new Int32Array(buffer);
function foo() {
  i32[0] = 0x12341234;
  var __v_3 = i32[0];
  return i16[0];
}

print(foo());

// Output:

# Compared x64,ignition with x64,ignition_turbo_opt
#
# Flags of x64,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1234 --ignition --turbo-filter=~ --hydrogen-filter=~ --validate-asm --nocrankshaft
# Flags of x64,ignition_turbo_opt:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1234 --ignition-staging --turbo --always-opt --validate-asm
#
# Difference:
- 4660
+ 305402420
#
# Source file:
none
#
### Start of configuration x64,ignition:
4660

### End of configuration x64,ignition
#
### Start of configuration x64,ignition_turbo_opt:
305402420

### End of configuration x64,ignition_turbo_opt
Project Member

Comment 2 by bugdroid1@chromium.org, Feb 28 2017

Project Member

Comment 3 by ClusterFuzz, Feb 28 2017

ClusterFuzz has detected this issue as fixed in range 43476:43477.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

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

Regressed: V8: 43107:43108
Fixed: V8: 43476:43477

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95YjQe9li7EXyeJ9_nCnpVQLog7Qn1ALEgzE5qHsuQN-MP7yB7yZ2YLmqTWZla-2njvFaRj-VBU4QMIpeoJcvzEebUrR6YbmzRXSJLJeg3gcuEaKYYwPg60OImr9FqnhqVk674HUjd2Jf914SUuRpdwBAVUmF0ZqNF0oOgnxp4KVEVLEZn9_0eeVyJY0xPCWdIoFxr_erMbG8B7WYJORz2ScgFrR9lUbWIhRgKAaNN_cFLQRab6y3j6k6BgZw8rDMF9XYRMfXZZgDwIcZEkFJsAdW3FeFpoxss-VPleDx0yZBCAiutke0LxXFiOzYtYHNiQeONyutGPCQJ3xK0E-efluG1g0UdWwZeAbdGf45OkFcB0saffuzgIWmQddLik4a2bX9mzT9Ye8xwmJspkJj1glqhFOg?testcase_id=6449692012707840


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, Feb 28 2017

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

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

Sign in to add a comment