diff options
author | vollick@chromium.org <vollick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-04-25 05:48:05 +0000 |
---|---|---|
committer | vollick@chromium.org <vollick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-04-25 05:48:05 +0000 |
commit | 62426903034bb346296e4b60c515fc55cbce1739 (patch) | |
tree | 6d2983b9cf5596e2cb84d02856348da0ae964c59 /cc/trees/layer_tree_host.h | |
parent | 6b1ad3be83fd52a22824de66f2b8518175e010ee (diff) | |
download | chromium_src-62426903034bb346296e4b60c515fc55cbce1739.zip chromium_src-62426903034bb346296e4b60c515fc55cbce1739.tar.gz chromium_src-62426903034bb346296e4b60c515fc55cbce1739.tar.bz2 |
If we give up on compositing, never try to reinitialize the renderer.
If the layer tree host calls DidRecreateOutputSurface(false), it means that
we've given up. We can't use compositing mode. Normally, the embedder takes this
as a cue to stop using the compositor. It looks like in this bug, we're forcing
the compositor back into action (possibly by trying to take a screenshot). This
patch adds a safeguard to prevent us from incorrectly attempting reinitialize
the renderer in this case.
BUG=174138
Review URL: https://chromiumcodereview.appspot.com/14238011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@196324 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc/trees/layer_tree_host.h')
-rw-r--r-- | cc/trees/layer_tree_host.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/cc/trees/layer_tree_host.h b/cc/trees/layer_tree_host.h index 134598f..f94066d 100644 --- a/cc/trees/layer_tree_host.h +++ b/cc/trees/layer_tree_host.h @@ -292,6 +292,7 @@ class CC_EXPORT LayerTreeHost : NON_EXPORTED_BASE(public RateLimiterClient) { int commit_number_; scoped_ptr<RenderingStatsInstrumentation> rendering_stats_instrumentation_; + bool renderer_can_be_initialized_; bool renderer_initialized_; bool output_surface_lost_; int num_failed_recreate_attempts_; |