CHECK failure: !i_isolate->has_scheduled_exception() in wasm-js.cc |
||
Issue descriptionDetailed 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.
,
Apr 26 2017
Yup. Fix for this is in-flight: https://codereview.chromium.org/2838143002/
,
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.
,
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.
,
Apr 27 2017
,
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 |
||
Comment 1 by mstarzinger@chromium.org
, Apr 26 2017Status: 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));