[Webkit-unassigned] [Bug 72078] [Chromium] Compositing with full sized fixed div causes heavy repaints

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jan 5 10:05:35 PST 2012


--- Comment #9 from Vangelis Kokkevis <vangelis at chromium.org>  2012-01-05 10:05:35 PST ---
(From update of attachment 121036)
I think this is a reasonable change and more in the spirit of how the reclaim limit should be functioning. Its role is not to actively go and delete textures over the limit but only do so if we need to allocate a new texture.  

There is still a remaining issue that we don't actually protect textures that we already have and need for the current frame from being deleted. So if we are over the reclaim limit and we get a new layer, there is a good chance we'll go and delete a texture from another layer that's still needed if that other layer comes later in the hierarchy traversal.

Maybe what we should be doing instead is to first reserve all the existing textures that we need for the frame before we try to create new ones.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list