New issue
Advanced search Search tips

Issue 902576 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jan 15
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug
Proj-VR
Proj-XR
Proj-XR-VR

Blocking:
issue 910748



Sign in to add a comment

Investigate desktop VR UI rendering on main thread vs dedicated thread

Project Member Reported by billorr@chromium.org, Nov 6

Issue description

There were issues with rendering on a background thread, because gfx::FontList's default constructor accesses a global scoped_refptr that is owned by the main thread.

Finalize the plan for whether VR rendering on the main thread is safe (won't incur extra latency or cause extra latency), or whether gfx types should be made more thread agnostic.
 
Blocking: 773882
Labels: VR-Desktop
cc has two versions - one for browser process where rendering happens on the main thread, and one for the renderer process where rendering happens on a background thread.  the argument there is that the main thread is not too busy in the browser process.  I think we are good here.
Blocking: -773882 910748
Status: WontFix (was: Assigned)
We are keeping things on the main thread. Closing this bug.

Sign in to add a comment