| commit | 22a55369c16d825d2f06df9be5bfeb44840ccab2 | |
| author | danakj <danakj@chromium.org> | |
| Wed, 11 Mar 2015 01:33:09 +0000 (10 18:33 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Wed, 11 Mar 2015 01:33:54 +0000 (11 01:33 +0000) | ||
| tree | bcf995cd968e4a5088b1130d7b5b4d920dfefdf8 | treesnapshot (tar.gz zip) |
| parent | e8b75463b2c7348bece9236ca4b84abbc1e222ed | commitdiff |
surfaces: Remove draw_and_swap_full_viewport_every_frame flag.
The draw_and_swap_full_viewport_every_frame flag causes the compositor
to try and draw even when its frame is incomplete. This was done in
order to support forced resource reclaiming, because when forced
resource reclaiming is on, we need to draw/swap even when there is no
damage (since the surface host has released the resources).
However, LayerTreeHostImpl::CalculateRenderPasses already checks
can_force_reclaim_resources and will not early out for no damage when it
is true. So this draw_and_swap_full_viewport_every_frame is not helping
the resource reclaiming case, and causes is to draw incomplete frames
instead.
R=jbauman
BUG=465861
Review URL: https://codereview.chromium.org/994223002
Cr-Commit-Position: refs/heads/master@{#320021}
The draw_and_swap_full_viewport_every_frame flag causes the compositor
to try and draw even when its frame is incomplete. This was done in
order to support forced resource reclaiming, because when forced
resource reclaiming is on, we need to draw/swap even when there is no
damage (since the surface host has released the resources).
However, LayerTreeHostImpl::CalculateRenderPasses already checks
can_force_reclaim_resources and will not early out for no damage when it
is true. So this draw_and_swap_full_viewport_every_frame is not helping
the resource reclaiming case, and causes is to draw incomplete frames
instead.
R=jbauman
BUG=465861
Review URL: https://codereview.chromium.org/994223002
Cr-Commit-Position: refs/heads/master@{#320021}
| cc/surfaces/surface_display_output_surface.cc | diffblobblamehistory |