• 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
..
DEPS Loading commit data...
OWNERS Loading commit data...
code-serializer.cc Loading commit data...
code-serializer.h Loading commit data...
deserializer.cc Loading commit data...
deserializer.h Loading commit data...
mksnapshot.cc Loading commit data...
natives-common.cc Loading commit data...
natives-external.cc Loading commit data...
natives.h Loading commit data...
partial-serializer.cc Loading commit data...
partial-serializer.h Loading commit data...
serializer-common.cc Loading commit data...
serializer-common.h Loading commit data...
serializer.cc Loading commit data...
serializer.h Loading commit data...
snapshot-common.cc Loading commit data...
snapshot-empty.cc Loading commit data...
snapshot-external.cc Loading commit data...
snapshot-source-sink.cc Loading commit data...
snapshot-source-sink.h Loading commit data...
snapshot.h Loading commit data...
startup-serializer.cc Loading commit data...
startup-serializer.h Loading commit data...