[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 #17 from Christopher Cameron <ccameron at chromium.org>  2012-08-23 14:38:10 PST ---
(In reply to comment #16)

> 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?

I agree with this, and would say that the main thread should eventually have no interaction with the PTM at all.

At the moment, the main thread's interaction with the PTM is that it
1. Sets priorities based on the viewport
2. Decides what it needs to re-paint (it checks to see if the backing has been destroyed).

For (1), the main thread isn't competent to do this (as enne pointed out)
For (2), I'd imagine that impl-side painting would move this off of the main thread (and of course, then, it doesn't have to worry about not knowing what textures the impl thread has destroyed).

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