Move AW renderer compositor context to gpu thread
commitd9e23a08df149f0483995f2463675f011e4d77ef
authorboliu <boliu@chromium.org>
Thu, 5 Feb 2015 01:25:22 +0000 (4 17:25 -0800)
committerCommit bot <commit-bot@chromium.org>
Thu, 5 Feb 2015 01:27:22 +0000 (5 01:27 +0000)
tree96e6009c900bce7197f9090357884bc110831556
parent0c7c18bfcea9d8c8b0f88558905221851d2b93ae
Move AW renderer compositor context to gpu thread

Use TexSubImage2D instead of TexImage2D to avoid orphaning
EGLImage
Create the renderer compositor context on the gpu thread.

BUG=448168, 259924

Committed: https://crrev.com/a4baed454be2bb165cb12eb7df432e9138e746e6
Cr-Commit-Position: refs/heads/master@{#313846}

Review URL: https://codereview.chromium.org/769703005

Cr-Commit-Position: refs/heads/master@{#314705}
content/browser/android/in_process/synchronous_compositor_factory_impl.cc
gpu/command_buffer/service/async_pixel_transfer_manager_android.cc
gpu/command_buffer/service/async_pixel_transfer_manager_idle.cc
gpu/command_buffer/service/async_pixel_transfer_manager_idle.h
gpu/command_buffer/service/async_pixel_transfer_manager_linux.cc
gpu/command_buffer/service/async_pixel_transfer_manager_mac.cc
gpu/command_buffer/service/async_pixel_transfer_manager_win.cc