Skip to content

GitLab

T
tangled
Switch branch/tag
  1. 23 Aug, 2018 3 commits
    • Wez's avatar
      Add missing ScopedTaskEnvironment to stop tests leaking TaskScheduler. · a9e0bfb9
      Wez authored 
      Bug: 875486
Change-Id: I448361ccdb91b83ab71c6eda34066e6e76c278de
Reviewed-on: https://chromium-review.googlesource.com/1185490Reviewed-by: default avatarRaymes Khoury <raymes@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#585323}
      a9e0bfb9
    • Kai Ninomiya's avatar
      Add optimized path for YUV-to-WebGL, remove old path · 321904d3
      Kai Ninomiya authored 
      For camera-to-WebGL on Nexus 6P at 720p, this improves blocking
texImage2D time from ~12ms to ~4ms (200% speedup). On some other
devices and resolutions, I think there can be up to a ~10x speedup.

* Adds an optimized upload path for CPU-side YUV video frames (e.g.
  those coming from a video camera on Android). This path uploads the
  individual Y/U/V textures to the GPU, performs a GPU YUV-RGB decode,
  and copies the result into the WebGL texture.

  This code path could potentially be further optimized in 2 ways:
    * Avoid the extra copy of the CPU-side YUV data from
      browser-renderer shared memory (VideoFrame::STORAGE_SHMEM) to
      renderer-gpu shared memory (transfer buffer, probably).
    * Avoid the extra copy from the decoded image (SkImage) into the
      WebGL texture, and instead decode directly into the WebGL texture.

* Removes an old GPU-GPU path that was obsoleted by
  CopyVideoTextureToPlatformTexture. This obsolete path was only
  handling CPU-GPU uploads instead of GPU-GPU uploads, and it was doing
  so by performing an expensive YUV-RGB conversion on the CPU.

  This also allowed some cleanup in TexImageHelperHTMLVideoElement.

Bug: 867368
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: Id25d5dbfc76ec8f9dc606890588a20978f6943f6
Reviewed-on: https://chromium-review.googlesource.com/1161606
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: default avatarMounir Lamouri <mlamouri@chromium.org>
Reviewed-by: default avatarKenneth Russell <kbr@chromium.org>
Reviewed-by: default avatarDan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#585322}
      321904d3
    • bsheedy's avatar
      Add VR browser omnibox keyboard input test · a0c12063
      bsheedy authored 
      Modifies an existing test that brings up a keyboard so that it also
inputs text via the keyboard. This is to catch future occurances of
https://crbug.com/874671 where inputting text into the VR Browser's
omnibox would cause a browser crash.

Also installs the latest VR Keyboard APK as part of pre-test setup
in test suites that could potentially use the keyboard.

Bug: 874671, 874696
Change-Id: Ic04d678e14de918fbf159078422c9d5459e8d98d
Reviewed-on: https://chromium-review.googlesource.com/1176876Reviewed-by: default avatarMichael Thiessen <mthiesse@chromium.org>
Reviewed-by: default avatarBen Pastene <bpastene@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#585321}
      a0c12063
  3. 22 Aug, 2018 37 commits