Closed Bug 1515886 Opened 6 years ago Closed 6 years ago

WebVR doesn't work properly when debugger/developer tools is opened since 64.0

Categories

(Core :: WebVR, defect)

64 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1514417

People

(Reporter: luca, Unassigned)

References

Details

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 Steps to reproduce: visit a simple webvr-project like https://webvr.info/samples/05-room-scale.html, or a complex one like our http://ostsee-life.nabu.de/en/ (starts in vr mode if headset connected) when firefox debugger/developer tools are opened. Tested with Oculus Rift and Oculus Driver Version 1.33.0.750915 Tried it on three different windows 10 systems. the problems only seems to appear since firefox version 64.0. Previous versions work properly. Actual results: The page appeares "blurry" in the headset with big black squares, rendering with very low fps (below 5). Only a full reboot seems to solve this behaviour Expected results: Without opening developer tools (during the entire session) the webvr projects run smoothly and as exprected on the same systems.
okay, after i tried this a few times im not entirely sure if this problem is that simple to reproduce. There seems to crash something webvr-related on http://ostsee-life.nabu.de/en/ which causes firefox to render only a single frame and a "waiting/hourglass" indicator in the headset. once this error is there it will stay, even if you close the page and visit another one like https://webvr.info/samples/05-room-scale.html for example.
Component: Untriaged → WebVR
Product: Firefox → Core

I think the weird graphic artifacts i described are results from the oculus' smoothing algorithms aynchronous space- and timewarp

https://developer.oculus.com/blog/asynchronous-spacewarp/

so the real problem is the low fps here, that the oculus rift driver than tries to extrapolate to a smoother experience.

The question then is: what causes firefox 64 to get to a point where the frames drop significantly until unusability, where firefox 63 had no problems?

we are trying to figure out the FPS drop issue from FF 64 at Bug 1514417.

See Also: → 1514417

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

we are trying to figure out the FPS drop issue from FF 64 at Bug 1514417.

yeah that seems to be the same issue we're experiencing

Thank you Luca for reporting this issue.
Based on comment 3 and comment 4 I am closing this issue as Duplicate of Bug 1514417.
This way the tracking process will be simplified.
Cheers!

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(cristian.comorasu)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.