| b17bbf2f0f3441ae7ec7478ff8f77cb8fb21bcb8 |
|
22-Aug-2013 |
Jonathan Dixon <joth@google.com> |
Patch in https://codereview.chromium.org/23234003
Bug: 9982214
Took un-submitted patchset 5
https://codereview.chromium.org/download/issue23234003_29001.diff
Applied cleanly to klp-dev + crrev.com/23072008
Original description:
Support stream textures with the synchronous compositor
This adds a thread-safe StreamTextureManager for GLInProcessContext.
It further adds some plumbing for the webkit thread to be able
to create a StreamTextureFactory from the main thread (see render_view_impl.cc)
with the ability to extract the thread-safe SurfaceTexture(Bridge) for a given stream.
This is nothing but a crazy amount of plumbing to achieve this:
- StreamTexture::Update() i.e. SurfaceTexture::updateTexImage needs to happen on the GL thread
with a current context
- The StreamTextureFactory and Proxy are referenced from the WebmediaPlayer instance which lives on
the main thread
- The callback for invalidating the video is posted to the
compositor thread directly (here: UI thread) bypassing the main thread
BUG=239760
Change-Id: I2a5e86ed580af0c4659583f4deda96a51fd5ba0c
/external/chromium_org/gpu/command_buffer/service/stream_texture_manager.h
|