[Webkit-unassigned] [Bug 77655] New: Support detaching TextureManager from ManagedTexture

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Feb 2 09:56:06 PST 2012


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

           Summary: Support detaching TextureManager from ManagedTexture
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: fischman at chromium.org
                CC: kbr at google.com, jamesr at chromium.org, enne at google.com


ManagedTexture stores a raw pointer to its TextureManager, so if a TextureManager is deleted, subsequent attempts to use the ManagedTexture behave erratically (mostly either crash or infinitely-loop as the now-deleted manager's hashtable is used to look for the texture's token).

As a result ManagedTexture's can't be cached/reused (see bug 77654 for one example where this bites <video>).

It would be nice if ManagedTexture could be made robust to its TextureManager being deleted.

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