(location_) != nullptr in handles.h |
|||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6606669360660480 Fuzzer: afl_v8_wasm_asmjs_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: (location_) != nullptr in handles.h Regressed: https://cluster-fuzz.appspot.com/revisions?job=afl_chrome_asan&range=415614:415641 Minimized Testcase (0.22 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94lX0b1qBnUyRc8Yw47IKc1jOGJZhgL9b2Pcl_MrFqV-mlizSJU0uwUoChiLFLiYWC1NC8v8PDffJGAj6EgCYbDG1JmHbfF5K9p7LY51fXoU_Fw76AoiI9W8SpQUfechHa7ThYZ9yPDFia8gczsQPWOdfQ5UA?testcase_id=6606669360660480 Issue manually filed by: mmoroz See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Sep 20 2016
,
Sep 22 2016
,
Sep 22 2016
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/447de9ae5b3ca027ec741147f7bc50de438d32f4 commit 447de9ae5b3ca027ec741147f7bc50de438d32f4 Author: ahaas <ahaas@chromium.org> Date: Thu Sep 22 14:23:32 2016 [wasm] Correctly handle the result of WasmModule::Instantiate in the wasm-module-runner WasmModule::Instantiate can return an empty handle if it is not possible to instantiate the module. With this change the wasm-module-runner does not assume anymore that WasmModule::Instantiate produces a valid handle. BUG= chromium:648078 R=titzer@chromium.org Review-Url: https://codereview.chromium.org/2365493003 Cr-Commit-Position: refs/heads/master@{#39629} [modify] https://crrev.com/447de9ae5b3ca027ec741147f7bc50de438d32f4/test/common/wasm/wasm-module-runner.cc
,
Sep 22 2016
,
Sep 24 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Sep 25 2016
ClusterFuzz has detected this issue as fixed in range 420585:420614. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6606669360660480 Fuzzer: afl_v8_wasm_asmjs_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: (location_) != nullptr in handles.h Regressed: https://cluster-fuzz.appspot.com/revisions?job=afl_chrome_asan&range=415614:415641 Fixed: https://cluster-fuzz.appspot.com/revisions?job=afl_chrome_asan&range=420585:420614 Minimized Testcase (0.22 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94lX0b1qBnUyRc8Yw47IKc1jOGJZhgL9b2Pcl_MrFqV-mlizSJU0uwUoChiLFLiYWC1NC8v8PDffJGAj6EgCYbDG1JmHbfF5K9p7LY51fXoU_Fw76AoiI9W8SpQUfechHa7ThYZ9yPDFia8gczsQPWOdfQ5UA?testcase_id=6606669360660480 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
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 mmoroz@chromium.org
, Sep 18 2016Components: Blink>JavaScript>WebAssembly
Owner: ahaas@chromium.org