1534591 - WebVR Oculus Rift Hourglass and very high latency

Status: RESOLVED DUPLICATE of bug 1514417

(Core :: WebVR, defect)

Description

[Nikodem G.]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Vivaldi/2.2.1388.37

Steps to reproduce:

On Firefox Quantum Version 65.0.2 (64 Bit) opening a WebVR sample Project, or any other WebVR project using the Oculus Rift causes after several interactions and some minutes passed to increase the latency greatly.

Good example:
https://webvr.info/samples/03-vr-presentation.html

Windows PC Specs are:
OS: Microsoft Windows 10 Pro Version 10.0.17763 Build 17763
CPU: i7-7700HQ
RAM: 16GB
GPU: NVIDIA GTX 1070
NVIDIA Driver Version: 419.35

Oculus-App-Version: 1.36.0.215623

I could reproduce this bug on 2 other machines with similar specs.

Actual results:

The latency increases greatly in seconds, until no interactions are possible anymore.
The Oculus Hour Glass shows up in VR mode.

The 3D Mode (when leaving VR) is working as it should (no issues, browser remains stable)

To solve this problem, the browser has to be restarted until the issue reappears again. Closing the tab and opening a new one does not work.

Expected results:

The VR View should not freeze and increase such a high amount of latency.

Comment 1

[Nikodem G.]

It seems that this issue occurs when using the windows version 10.0.17763. On a prior Version the bug did not occur.
Tested this on this page:
https://webvr.info/samples/03-vr-presentation.html

After 3-5 minutes and interacting with some buttons of the rift controllers the latency increased.

Comment 2

[Daosheng Mu[:daoshengmu]]

Hi Nikodem,
Thanks for making us know. We seem to already fix this issue at Bug 1514417, I encourage you have a try in Firefox 66 or 67 (Nightly). I would expect this problem should be resolved.

Comment 3

[Nikodem G.]

(In reply to Daosheng Mu[:daoshengmu] from comment #2)

Hi Nikodem,
Thanks for making us know. We seem to already fix this issue at Bug 1514417, I encourage you have a try in Firefox 66 or 67 (Nightly). I would expect this problem should be resolved.

Hello Daosheng,
I can confirm that this Bug does not occur on Nightly 67,
but does occur on the newest Firefox Quantum (65.02).

Will the Nightly fix also be applied to a new Firefox Quantum release?

Thank you and
Best Regards
Nikodem

Comment 4

[Daosheng Mu[:daoshengmu]]

yes. We gonna release Firefox 66 on 2019-03-19. This fix should be at FF 66 already. Thanks for your help :)

Comment 5

[Nikodem G.]

(In reply to Daosheng Mu[:daoshengmu] from comment #4)

yes. We gonna release Firefox 66 on 2019-03-19. This fix should be at FF 66 already. Thanks for your help :)

Thanks for the Info :).

Ill check it out and resolve this once tested on the new version.

Best Regards
Niko