New issue
Advanced search Search tips

Issue 715623 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Feature
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

Assess performance of native texture rendering for VR UI

Project Member Reported by cjgrant@chromium.org, Apr 26 2017

Issue description

Currently, the skia-generated textures used for WebVR warnings are rendered once, on VR startup.

In the v0 browser UI, textures such as buttons and the URL bar must (at times) be updated between frames.  For example, when the page URL changes, a new texture must be rendered.

The current plan is to do all texture rendering via SW/raster rather than GL-backed canvases.  This means there is CPU-side overhead in updating textures, and pushing the updates to the GPU.  Gut feeling is that these won't be heavy operations, but we should verify this.


 
Labels: hotlist-initial-vr-browser
Labels: -hotlist-initial-vr-browser
Status: Fixed (was: Untriaged)

Sign in to add a comment