084207d968
Using the Isolate's allocator when creating the WasmModule can lead to use-after-free situations when the NativeModule is shared across Isolates. R=mstarzinger@chromium.org Bug: v8:9079 Change-Id: I5a564852179cc5b9d4cbad2a002d3b6e14b01968 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1550404 Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60605} |
||
---|---|---|
.. | ||
control-transfer-unittest.cc | ||
decoder-unittest.cc | ||
function-body-decoder-unittest.cc | ||
leb-helper-unittest.cc | ||
loop-assignment-analysis-unittest.cc | ||
module-decoder-unittest.cc | ||
OWNERS | ||
streaming-decoder-unittest.cc | ||
trap-handler-posix-unittest.cc | ||
trap-handler-win-unittest.cc | ||
trap-handler-x64-unittest.cc | ||
wasm-code-manager-unittest.cc | ||
wasm-compiler-unittest.cc | ||
wasm-macro-gen-unittest.cc | ||
wasm-module-builder-unittest.cc | ||
wasm-opcodes-unittest.cc |