summaryrefslogtreecommitdiffstats
path: root/base/base.gypi
diff options
context:
space:
mode:
authordanakj <danakj@chromium.org>2014-10-24 11:50:40 -0700
committerCommit bot <commit-bot@chromium.org>2014-10-24 18:51:08 +0000
commit11f13546fd3ee3d53921c23861bf970bd2bb6428 (patch)
tree2b737e7749af988d2acc0a9ebe458c659d246089 /base/base.gypi
parent0e2deda3f0c59c8fc18323ede48a552bef341c24 (diff)
downloadchromium_src-11f13546fd3ee3d53921c23861bf970bd2bb6428.zip
chromium_src-11f13546fd3ee3d53921c23861bf970bd2bb6428.tar.gz
chromium_src-11f13546fd3ee3d53921c23861bf970bd2bb6428.tar.bz2
cc: Always keep the PictureLayerImpl::twin_layer_ pointer valid.
We currently null the twin_layer_ pointer when pushing to the active tree and then using hashmap lookups to find the recycled twin, and reconnecting the pointers in DoPostCommitInitializationIfNeeded(). Instead, we can leave the pointers always valid and use Getter methods that check what tree the twin is on to decide if we should consider it a pending twin or a recycle twin. This means that during commit the pending layer will be able to find its active twin when it updates its picture pile, so that it can share tiles that are not invalidated. (Previously it wouldn't know about its twin until after commit, when we set it up and then did SyncTilings.) This allows us to have a more straightforward flow of data, setting up the pending tilings when we give it a pile from the main thread instead of doing it at some hazy future time (usually inside UpdateDrawProperties). R=enne, vmpstr BUG=407418,387116 Review URL: https://codereview.chromium.org/676953003 Cr-Commit-Position: refs/heads/master@{#301155}
Diffstat (limited to 'base/base.gypi')
0 files changed, 0 insertions, 0 deletions