Investigate desktop VR UI rendering on main thread vs dedicated thread |
||
Issue descriptionThere 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.
,
Jan 15
We are keeping things on the main thread. Closing this bug. |
||
►
Sign in to add a comment |
||
Comment 1 by billorr@chromium.org
, Dec 7Labels: VR-Desktop