• gdeepti's avatar
    [wasm] Do not unregister an ArrayBuffer if it is already external · e2fc979e
    gdeepti authored
     - Currently if GrowMemory is called with pages = 0, an attempt is made to
       unregister the ArrayBuffer even if it is external. Cleanup so all Detaching
       of ArrayBuffer is centralized to one method, and can only be called fromJS.
     - Gate creating WeakHandles to the memory on the buffer having guard pages
       enabled. Currently creating a WeakHandle is gated only on if the buffer
       is_external true. If a buffer is marked is_external = true to begin with,
       the WeakHandle is created and the Finalizer is run causing the program to
       crash.
    
    BUG=chromium:717647
    
    Review-Url: https://codereview.chromium.org/2867233002
    Cr-Commit-Position: refs/heads/master@{#45238}
    e2fc979e
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
fuzzer Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mkgrokdump Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...