• jkummerow's avatar
    [deserializer] Make large object deserialization GC safe · 6bfee50e
    jkummerow authored
    When black allocation is turned on at deserialization time, then
    slots in deserialized objects have to be visited by the incremental
    marker. For spaces with reservations, this has always been done; for
    large object space with its special handling, this patch adds it.
    
    Additionally, we must ensure that no incremental steps that might
    cause incremental marking to finish are performed while there is an
    AlwaysAllocateScope around.
    
    BUG=chromium:718859
    
    Review-Url: https://codereview.chromium.org/2868103002
    Cr-Commit-Position: refs/heads/master@{#45231}
    6bfee50e
Name
Last commit
Last update
benchmarks Loading commit data...
build_overrides Loading commit data...
docs Loading commit data...
gni Loading commit data...
gypfiles Loading commit data...
include Loading commit data...
infra Loading commit data...
samples Loading commit data...
src Loading commit data...
test Loading commit data...
testing Loading commit data...
third_party Loading commit data...
tools Loading commit data...
.clang-format Loading commit data...
.gitignore Loading commit data...
.gn Loading commit data...
.ycm_extra_conf.py Loading commit data...
AUTHORS Loading commit data...
BUILD.gn Loading commit data...
CODE_OF_CONDUCT.md Loading commit data...
ChangeLog Loading commit data...
DEPS Loading commit data...
LICENSE Loading commit data...
LICENSE.fdlibm Loading commit data...
LICENSE.strongtalk Loading commit data...
LICENSE.v8 Loading commit data...
LICENSE.valgrind Loading commit data...
Makefile Loading commit data...
Makefile.android Loading commit data...
OWNERS Loading commit data...
PRESUBMIT.py Loading commit data...
README.md Loading commit data...
WATCHLISTS Loading commit data...
codereview.settings Loading commit data...
snapshot_toolchain.gni Loading commit data...