[Webkit-unassigned] [Bug 76934] [chromium] Dirty pre-painted tiles should be deleted on impl side

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=76934





--- Comment #5 from David Reveman <reveman at chromium.org>  2012-01-25 08:10:35 PST ---
(In reply to comment #1)
> I don't think this is needed.
> 
> During every commit, we toss every tile on the impl side and then only sync the valid and non-dirty ones over.  Take a look at TiledLayerChromium::pushPropertiesTo.

It shouldn't be possible to get artifacts from the current system. Dana and I talked about this yesterday. This isn't really a problem with the current system, it's just an observation:

Dirty tile textures are not actually deleted (as in context3D->deleteTexture being called).

That's part of the design and the texture manager's ability to reuse textures. Would we want some exceptions to this now that we we have pre-painting? I guess it could possibly be worth not deleting dirty non-visible tile textures but deleting dirty non-visible pre-painted tile textures. Basically having a different memory limit for pre-painted tiles. I'm not convinced but figured raising the question wouldn't hurt.

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