New issue
Advanced search Search tips

Issue 709772 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

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

Project Member Reported by ClusterFuzz, Apr 8 2017

Issue description

Cc: bmeu...@chromium.org jarin@chromium.org mstarzinger@chromium.org
Components: -Blink>JavaScript Blink>JavaScript>Compiler
Labels: -Pri-1 Pri-2
Status: Available (was: Untriaged)
// PTAL. Ignition vs. turbofan error message difference. Repro:

function foo() {
  return { apply: Function.prototype.apply }.apply();
}

try {
  foo();
} catch (e) {}

%OptimizeFunctionOnNextCall(foo);

try {
  foo();
} catch (e) {
  print("Caught: " + e.message);
}

// Output:
# Compared x64,ignition with x64,ignition_turbo
#
# Flags of x64,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 732681078 --ignition --turbo-filter=~ --hydrogen-filter=~ --nocrankshaft
# Flags of x64,ignition_turbo:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 732681078 --ignition --turbo
#
# Difference:
- Caught: Function.prototype.apply was called on #<Object>, which is a object and not a function
+ Caught: (intermediate value).apply is not a function
#
### Start of configuration x64,ignition:
Caught: Function.prototype.apply was called on #<Object>, which is a object and not a function

### End of configuration x64,ignition
#
### Start of configuration x64,ignition_turbo:
Caught: (intermediate value).apply is not a function

### End of configuration x64,ignition_turbo

Project Member

Comment 2 by ClusterFuzz, May 16 2017

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

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

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
  sources: 308
  
Sanitizer: address (ASAN)

Regressed: V8: 43348:43349
Fixed: V8: 45316:45317

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


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.
not fixed
 Issue 727656  has been merged into this issue.
Project Member

Comment 5 by ClusterFuzz, Jun 21 2017

ClusterFuzz has detected this issue as fixed in range 46040:46041.

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

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
  sources: 308
  
Sanitizer: address (ASAN)

Regressed: V8: 43348:43349
Fixed: V8: 46040:46041

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


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 6 by ClusterFuzz, Jun 21 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Available)
ClusterFuzz testcase 4841135825747968 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