[Webkit-unassigned] [Bug 95057] [chromium] Allow impl-thread deletion of only some resources

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Sep 6 11:24:57 PDT 2012


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





--- Comment #49 from Eric Penner <epenner at chromium.org>  2012-09-06 11:25:12 PST ---
(In reply to comment #48)
> (In reply to comment #41)
> > I know this isn't intended to be complete yet, but the big missing piece in my mind is how you intend to delete 'only some resources', as the name of this CL implies.
> 
> That would fit in at CCPrioritizedTextureManager::reduceMemoryOnImplThread, where we'd put only some Backing*s into backingsToEvict.  The reduceMemoryOnImplThread will take a priority cutoff (and maybe a hard limit too).  Before adding that, I'll need to push priorities over to the Backing*s themselves.
> 
> > Currently we only push raw texture ids over to the impl thread. How do you intend to delete some of those raw IDs in all layers that contain them?
> 
> We just let the now-invalid raw IDs languish in the impl tree.  We disable drawing from the tree until we get a commit that was done when the main thread knew about all of the evictions (which guarantees that the impl tree no longer has invalid IDs).
> 
> I'd like to not require a commit, and have the impl tree be able to prune out the invalid part (and be able to determine "can I draw with the resources that are left?"), but that is a more long-term project.

I see. This all sounds good. I was worried we would need the long term project before this would be beneficial. The intermediate sounds good! (waiting for a commit to be able to draw).  Thanks for the clarification.

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