On 3/6/17 3:03 PM, kearw...@kearwood.com wrote:
The underlying VR API's expect this process to persist for the browser's lifespan and to have mutually-exclusive access to input from the headsets. It seems that the GPU process is the best fit afaict.
In case it matters, the GPU process does not have "persist for the browser lifespan" as a goal. In fact, the whole point of the GPU process is that driver crashes should take down the GPU process but not the browser. We then restart the GPU process as needed. On some hardware/software configurations, this is apparently not a rare occurrence.
-Boris _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
