!has_pending_exception() in isolate.cc |
||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6718260089454592 Fuzzer: mbarbella_js_mutation Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !has_pending_exception() in isolate.cc Regressed: V8: r34586:34587 Minimized Testcase (0.32 Kb): Download: https://cluster-fuzz.appspot.com/download/AMIfv94R2o0VRlP8sCjtx_zZ3hAtkzTQohzUruOK-uOmm3ug5nF8eEUkSTSZdw-P8Vi9HOfExg2HDhGuqh_xHN1oYFuwCtye8FEpNRQlU_w94HlVtf5_qFdhmxyWZ-Nl-dAxQBpt70TIeGFRZOD_RZoYyBjGK72e0g?testcase_id=6718260089454592 try { (function __f_2 () { })(); ( { })(); } catch(e) {; } function __f_3() { return { then: function() { } }; } try { ( { })(); } catch(e) {; } function __f_9() { } function __f_10() { try { __f_10(); } catch(e) { __v_9 = Wasm.instantiateModuleFromAsm( __f_9.toString()); /()()/.__f_10(); } } __f_10(); Filer: mstarzinger See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Aug 4 2016
,
Aug 4 2016
This seems un-related to asm.js. For the shorter test case below we get the use asm missing error which is expected.
function __f_9() {
}
function __f_10() {
__v_9 = Wasm.instantiateModuleFromAsm( __f_9.toString());
}
__f_10();
,
Aug 4 2016
The error specifically occurs in the following piece of code:
( {
})();
It occurs even without --expose-wasm
,
Aug 5 2016
seems like problem in asm instantiate itself. Please ignore previous comments.
,
Aug 23 2016
ClusterFuzz has detected this issue as fixed in range 38805:38806. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6718260089454592 Fuzzer: mbarbella_js_mutation Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !has_pending_exception() in isolate.cc Regressed: V8: r34586:34587 Fixed: V8: r38805:38806 Minimized Testcase (0.32 Kb): Download: https://cluster-fuzz.appspot.com/download/AMIfv94R2o0VRlP8sCjtx_zZ3hAtkzTQohzUruOK-uOmm3ug5nF8eEUkSTSZdw-P8Vi9HOfExg2HDhGuqh_xHN1oYFuwCtye8FEpNRQlU_w94HlVtf5_qFdhmxyWZ-Nl-dAxQBpt70TIeGFRZOD_RZoYyBjGK72e0g?testcase_id=6718260089454592 try { (function __f_2 () { })(); ( { })(); } catch(e) {; } function __f_3() { return { then: function() { } }; } try { ( { })(); } catch(e) {; } function __f_9() { } function __f_10() { try { __f_10(); } catch(e) { __v_9 = Wasm.instantiateModuleFromAsm( __f_9.toString()); /()()/.__f_10(); } } __f_10(); 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.
,
Aug 23 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mstarzinger@chromium.org
, Aug 4 2016Owner: rossberg@chromium.org
Status: Assigned (was: Untriaged)