• Michael Lippautz's avatar
    [heap] Introduce on-hold concurrent marking work list · b7e6eb92
    Michael Lippautz authored
    When hitting objects that are allocated in the most recent lienar
    allocation area, the concurrent marker currently has to bail out to the
    main thread.
    
    However, we only have to delay processing those objects until we are at
    a safepoint, e.g. IM::Step(). With this change we flush those
    on-hold-objects back to the shared queue upon performing an incremental
    marking step.
    
    Bug: chromium:694255
    Change-Id: I25647d0fc581a5c4de0346bc394dc51062f65f70
    Reviewed-on: https://chromium-review.googlesource.com/707315
    Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
    Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#48424}
    b7e6eb92
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...