New issue
Advanced search Search tips

Issue 722004 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 718739
Owner:
Closed: May 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, May 13 2017

Issue description

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

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: 4eb
  
Sanitizer: address (ASAN)

Regressed: V8: 45011:45012

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


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Owner: ahaas@chromium.org
Status: Assigned (was: Untriaged)
Owner: mstarzinger@chromium.org
Repro:
let v = {
  valueOf: function fn() {
    print(fn.caller);
  }
};
let g = f => f();
g(() => Number(v));


In default config:
function Number() { [native code] }

With --always-opt:
() => Number(v)

Cc: mstarzinger@chromium.org
 Issue 722109  has been merged into this issue.
Mergedinto: 718739
Status: Duplicate (was: Assigned)
Project Member

Comment 6 by ClusterFuzz, May 16 2017

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

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

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: 4eb
  
Sanitizer: address (ASAN)

Regressed: V8: 45011:45012
Fixed: V8: 45316:45317

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


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.

Sign in to add a comment