[Webkit-unassigned] [Bug 66434] New: [chromium] Update VideoLayerChromium to not access GC3D on the main thread
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Aug 17 16:55:53 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=66434
Summary: [chromium] Update VideoLayerChromium to not access
GC3D on the main thread
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebCore Misc.
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: enne at google.com
CC: jamesr at chromium.org, nduca at chromium.org,
husky at google.com
Blocks: 66430
VideoLayerChromium needs to be refactored to not access layerRenderer() or layerRendererContext(). The only GC3D that should be accessed is during updateCompositorResources.
This also means that resource deletion (via the destructor, for example) needs to be deferred until the next commit as the GC3D is not immediately available. I'm not sure of the best way to do this. These texture IDs need to be put on a queue either in the TextureManager or perhaps via some out-of-band message to the compositor thread.
--
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