• 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
..
barrier-unittest.cc Loading commit data...
bitmap-unittest.cc Loading commit data...
embedder-tracing-unittest.cc Loading commit data...
gc-idle-time-handler-unittest.cc Loading commit data...
gc-tracer-unittest.cc Loading commit data...
heap-unittest.cc Loading commit data...
item-parallel-job-unittest.cc Loading commit data...
marking-unittest.cc Loading commit data...
memory-reducer-unittest.cc Loading commit data...
scavenge-job-unittest.cc Loading commit data...
slot-set-unittest.cc Loading commit data...
spaces-unittest.cc Loading commit data...
unmapper-unittest.cc Loading commit data...
worklist-unittest.cc Loading commit data...