New issue
Advanced search Search tips

Issue 715017 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: !i_isolate->has_scheduled_exception() in wasm-js.cc

Project Member Reported by ClusterFuzz, Apr 25 2017

Issue description

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

Fuzzer: v8_builtins_generator
Job Type: linux_asan_d8_v8_arm64_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !i_isolate->has_scheduled_exception() in wasm-js.cc
  
Sanitizer: address (ASAN)

Regressed: V8: 44796:44797

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


Issue manually filed by: mstarzinger

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Owner: yangguo@chromium.org
Status: Assigned (was: Untriaged)
Unrelated to WASM. The {console.error} implementation seems to leave a scheduled exception behind that will be picked up by the next API call. The following is a simplified repro:

var e = new Error(); 
Object.defineProperty(e, "name", { get: function() { throw "boom" }}); 
console.error(e);  // Does not print, nor throw.
assertDoesNotThrow(() => print(23));
Yup. Fix for this is in-flight: https://codereview.chromium.org/2838143002/
Project Member

Comment 3 by ClusterFuzz, Apr 26 2017

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

Fuzzer: v8_builtins_generator
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !isolate_->external_caught_exception() in api.cc
  
Sanitizer: address (ASAN)

Regressed: V8: 44853:44854

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


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

Comment 4 by ClusterFuzz, Apr 27 2017

ClusterFuzz has detected this issue as fixed in range 44879:44880.

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

Fuzzer: v8_builtins_generator
Job Type: linux_asan_d8_v8_arm64_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !i_isolate->has_scheduled_exception() in wasm-js.cc
  
Sanitizer: address (ASAN)

Regressed: V8: 44796:44797
Fixed: V8: 44879:44880

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


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.
Status: Fixed (was: Assigned)
Project Member

Comment 6 by ClusterFuzz, May 11 2017

ClusterFuzz has detected this issue as fixed in range 45246:45247.

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

Fuzzer: v8_builtins_generator
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !isolate_->external_caught_exception() in api.cc
  
Sanitizer: address (ASAN)

Regressed: V8: 44853:44854
Fixed: V8: 45246:45247

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


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