CHECK failure: !thrower.error() in wasm-module.cc |
||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5044757742223360 Fuzzer: inferno_js_fuzzer Job Type: linux_ubsan_vptr_d8 Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !thrower.error() in wasm-module.cc Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=470050:470073 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5044757742223360 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
May 30 2017
ClusterFuzz has detected this issue as fixed in range 475250:475395. Detailed report: https://clusterfuzz.com/testcase?key=5044757742223360 Fuzzer: inferno_js_fuzzer Job Type: linux_ubsan_vptr_d8 Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: !thrower.error() in wasm-module.cc Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=470050:470073 Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=475250:475395 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5044757742223360 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.
,
May 30 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by clemensh@chromium.org
, May 26 2017Status: Assigned (was: Untriaged)