[Webkit-unassigned] [Bug 96463] [chromium] Evict textures through the texture manager instead of the resource provider

[bugzilla-daemon at webkit.org]

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


Christopher Cameron <ccameron at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |danakj at chromium.org,
                   |                            |enne at google.com,
                   |                            |epenner at chromium.org




--- Comment #2 from Christopher Cameron <ccameron at chromium.org>  2012-09-11 20:27:22 PST ---
This is the second-to-last slice of bug 95057.  The one remaining slice is partial clears of the texture upload queue (which is big enough self-contained enough to warrant a separate change).

Synopsis from ChangeLog:

When deleting contents textures' resources on the impl thread, do the deletion through the CCPrioritizedTextureManager instead of the CCResourceProvider.

This requires traversing the backings list on the impl thread while the main thread is running, so remove the one remaining traversal of  backings list by the main thread. This traversal happens when unlinking textures that were evicted by the impl thread, so explicitly send the list of evicted backings from the impl thread to the main thread.

Unify all resource deletion paths in the CCPrioritizedTextureManager. Always perform the sequence of eviction (deleting the GL resource) and then destruction of evicted backings (deleting the objects).  Also, use the same function (evictBackingsToReduceMemory) to reduce memory consumption both during commit and when done by the impl thread in response to a request by the GPU memory manager.

Note that destroying only some of the resources at a time during texture eviction (as opposed all resources) is still not supported because the texture upload queues cannot be only-partially invalidated yet. Updated tests to take this behavior into account.

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