Issue metadata
Sign in to add a comment
|
CHECK failure: WasmInstanceObject::IsWasmInstanceObject(*instance_obj) in runtime-test.cc |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6586504922267648 Fuzzer: inferno_js_fuzzer Job Type: windows_asan_d8 Platform Id: windows Crash Type: CHECK failure Crash Address: Crash State: WasmInstanceObject::IsWasmInstanceObject(*instance_obj) in runtime-test.cc v8::platform::PrintStackTrace v8::internal::Runtime_WasmNumInterpretedCalls Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=457847:458431 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6586504922267648 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Aug 12 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
,
Aug 12 2017
,
Aug 14 2017
,
Aug 14 2017
,
Aug 16 2017
The test case was invalid from the beginning. The fix was to avoid generating such tests in the future.
,
Sep 18 2017
We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.
,
Nov 23 2017
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sheriffbot@chromium.org
, Aug 12 2017