summaryrefslogtreecommitdiffstats
path: root/cc/tile_manager.h
diff options
context:
space:
mode:
authornduca@chromium.org <nduca@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-02-16 07:24:59 +0000
committernduca@chromium.org <nduca@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-02-16 07:24:59 +0000
commit463ced3134201e61869dcb73c2bd56219512ce37 (patch)
tree5bcc66171ddccf60759689bb2869c14b090d245f /cc/tile_manager.h
parent9c14ff54e675f0179a097a82e51286220b24252d (diff)
downloadchromium_src-463ced3134201e61869dcb73c2bd56219512ce37.zip
chromium_src-463ced3134201e61869dcb73c2bd56219512ce37.tar.gz
chromium_src-463ced3134201e61869dcb73c2bd56219512ce37.tar.bz2
[cc] Sort tiles based on distance to screen after time, and before content rect
When the page is stationary, we break ties based on the content rect coordinates of the tiles. This causes us to basically ignore the worldspace importance of the tile completely! This means that when the viewport stops moving, and you have anything with more than one layer, far far far offscreen layers suddenly start getting memory. Big thanks to @vangelis for figuring this out. BUG=176645 Review URL: https://chromiumcodereview.appspot.com/12287023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@182952 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc/tile_manager.h')
-rw-r--r--cc/tile_manager.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/cc/tile_manager.h b/cc/tile_manager.h
index 1e0de2e..e05217b 100644
--- a/cc/tile_manager.h
+++ b/cc/tile_manager.h
@@ -97,6 +97,7 @@ class CC_EXPORT ManagedTileState {
TileManagerBin gpu_memmgr_stats_bin;
TileResolution resolution;
float time_to_needed_in_seconds;
+ float distance_to_visible_in_pixels;
};
// This class manages tiles, deciding which should get rasterized and which