Direct-leak in v8::ArrayBufferAllocator::Allocate |
||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5386158370717696 Fuzzer: libfuzzer_v8_wasm_code_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: v8::ArrayBufferAllocator::Allocate v8::internal::wasm::NewArrayBuffer AllocateMemory Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94ElkgzeQQHubLiE7RVGNxuxV9zILvt_vrZ5nB5CdD0Gao2VnBAMUUYGbewkL6ohFx424qjkxpi0tXMYLPeQrlQUXfjMuUfYuRxSMxiuoUYvCWfEudlJROOOHtx_TmdkqGog2WAgB12arYQVur1HKNBH8uRAg?testcase_id=5386158370717696 Issue manually filed by: mmoroz See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Sep 2 2016
,
Oct 4 2016
I cannot reproduce this issue.
,
Oct 4 2016
CF also says that it is not reproducible now.
,
Oct 4 2016
The binary format of WebAssembly changed recently. I think the issue here could still exist but gets triggered by a different input.
,
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 1 2016Components: Blink>JavaScript>WebAssembly
Owner: ahaas@chromium.org