| commit | a8934faf9912c921e0ebfe2811e43357fb46c266 | |
| author | sievers <sievers@chromium.org> | |
| Wed, 26 Nov 2014 22:50:17 +0000 (26 14:50 -0800) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Wed, 26 Nov 2014 22:50:48 +0000 (26 22:50 +0000) | ||
| tree | cebb52d4b007bb6170aa4ad8ba3ba778d2c7e3c0 | treesnapshot (tar.gz zip) |
| parent | 32dbd658750c7789efabbb5529d6fd54a73d4556 | commitdiff |
Remove ImageTransportFactoryAndroid
GLHelper on Android should only be used for doing post-readback
work. So hide the GLHelper singleton in RWHVAndroid.
This is because on Android we cannot support synchronously
creating a context and returning a GLHelper when the GPU thread
is run out of process. Instead we rely on the browser compositor
to take care of setting up the channel and deferring composite
until it's ready.
Remove one call site that was using GLHelper on Android from
VideoCaptureController, which doesn't need to worry about
browser-side sync points since it doesn't share textures with
the renderer.
NOTRY=True
Review URL: https://codereview.chromium.org/756373002
Cr-Commit-Position: refs/heads/master@{#305910}
GLHelper on Android should only be used for doing post-readback
work. So hide the GLHelper singleton in RWHVAndroid.
This is because on Android we cannot support synchronously
creating a context and returning a GLHelper when the GPU thread
is run out of process. Instead we rely on the browser compositor
to take care of setting up the channel and deferring composite
until it's ready.
Remove one call site that was using GLHelper on Android from
VideoCaptureController, which doesn't need to worry about
browser-side sync points since it doesn't share textures with
the renderer.
NOTRY=True
Review URL: https://codereview.chromium.org/756373002
Cr-Commit-Position: refs/heads/master@{#305910}