Don't ResetHandleVisibilityChanged in frames that don't draw |
||
Issue descriptionIf --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.
,
Jan 24 2018
This one is actually regardless of --check-damage-early, I think.
,
Jun 18 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by jamwalla@chromium.org
, Jan 24 2018