diff options
| author | enne@chromium.org <enne@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-11-05 22:38:51 +0000 |
|---|---|---|
| committer | enne@chromium.org <enne@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-11-05 22:38:51 +0000 |
| commit | bac0e556066f3b10a46a0c479a25096acc07e40c (patch) | |
| tree | ee769163851dd08b21f11148dee67730996d451b /cc/scheduler/scheduler.h | |
| parent | 86137956129413201db0be8c9d94f601b63ade61 (diff) | |
| download | chromium_src-bac0e556066f3b10a46a0c479a25096acc07e40c.zip chromium_src-bac0e556066f3b10a46a0c479a25096acc07e40c.tar.gz chromium_src-bac0e556066f3b10a46a0c479a25096acc07e40c.tar.bz2 | |
cc: Don't ManageTiles twice in one frame
Any external callers of ManageTiles should inform the Scheduler that
ManageTiles happened so that (1) it can clear the "needs manage tiles"
flag and (2) it can avoid doing a second ManageTiles on the same frame.
Other than after commit, where ManageTiles needs to be called
immediately in order to kick off new raster tasks (or determine that no
raster tasks are required to activate the tree), ManageTiles just needs
to be called periodically to keep the raster jobs working on the most
important content. Delaying the periodic caller to prevent these bad
frames with commits is a worthwhile tradeoff.
R=brianderson@chromium.org
BUG=314882
Review URL: https://codereview.chromium.org/45923005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@233111 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc/scheduler/scheduler.h')
| -rw-r--r-- | cc/scheduler/scheduler.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/cc/scheduler/scheduler.h b/cc/scheduler/scheduler.h index 1a284f1..e4a8bf3 100644 --- a/cc/scheduler/scheduler.h +++ b/cc/scheduler/scheduler.h @@ -91,6 +91,7 @@ class CC_EXPORT Scheduler { void FinishCommit(); void BeginMainFrameAborted(bool did_handle); + void DidManageTiles(); void DidLoseOutputSurface(); void DidCreateAndInitializeOutputSurface(); bool HasInitializedOutputSurface() const { |