[Webkit-unassigned] [Bug 94751] [chromium] Use an opaque type for texture priority

[bugzilla-daemon at webkit.org]

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





--- Comment #16 from Adrienne Walker <enne at google.com>  2012-08-23 14:31:07 PST ---
(In reply to comment #15)
> (In reply to comment #14)
> > (In reply to comment #13)
> >
> > What about making the texture manager thread-safe and accessible by both threads? I feel like this need has come up before (removing just some textures without a commit) and I suspect impl-side painting is going to need to touch on this as well.
> 
> Main thread is blocked when the PTM sorts all the textures by priority. This sorted list shouldn't be modified when the main thread isn't blocked, IIRC? So impl should be able to just read that list and drop the top textures from it until satisfied. And main thread should be able to do the same later and make the same choices?

Well, it's more than that, though.  I think the impl thread is eventually going to need to be able to reprioritize on its own somehow.  What if you've scrolled a whole bunch while the main thread was churning on Javascript and you suddenly need to toss out some textures?

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