New issue
Advanced search Search tips

Issue 805673 link

Starred by 0 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Don't ResetHandleVisibilityChanged in frames that don't draw

Project Member Reported by jamwalla@chromium.org, Jan 24 2018

Issue description

If --check-damage-early is enabled (from crrev.com/c/767851), LayerTreeImpl::ResetHandleVisibilityChanged is called in LayerTreeHostImpl::CalculateRenderPasses if there is damage. If the frame is aborted, though, we might not clear that damage even though we reset |handle_visibility_changed| and lose track of that damage.

Possibly, we should move the call to ResetHandleVisibilityChanged to after the last possible place that the frame could have been aborted.

thanks danakj@ for this suggestion.
 
Description: Show this description

Comment 2 by danakj@chromium.org, Jan 24 2018

This one is actually regardless of --check-damage-early, I think.
Owner: boliu@chromium.org

Sign in to add a comment