DCHECK failure in Code::WASM_TO_JS_FUNCTION == js_wrapper->kind() in wasm-interpreter.cc |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4749425393270784 Fuzzer: ochang_js_fuzzer Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: Code::WASM_TO_JS_FUNCTION == js_wrapper->kind() in wasm-interpreter.cc UnwrapWasmToJSWrapper CallExternalJSFunction Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48037:48038 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4749425393270784 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Oct 5 2017
,
Oct 5 2017
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 5 2017
,
Oct 5 2017
No security implications.
,
Oct 17 2017
ClusterFuzz has detected this issue as fixed in range 48580:48581. Detailed report: https://clusterfuzz.com/testcase?key=4749425393270784 Fuzzer: ochang_js_fuzzer Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: Code::WASM_TO_JS_FUNCTION == js_wrapper->kind() in wasm-interpreter.cc UnwrapWasmToJSWrapper CallExternalJSFunction Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48037:48038 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48580:48581 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4749425393270784 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Oct 17 2017
ClusterFuzz testcase 4749425393270784 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mstarzinger@chromium.org
, Oct 5 2017Owner: clemensh@chromium.org
Status: Assigned (was: Untriaged)