New issue
Advanced search Search tips

Issue 901861 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Proj-VR
Proj-XR



Sign in to add a comment

WebVR Token: twice RequestAnimation per frame

Reported by p...@sketchfab.com, Nov 5

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

Steps to reproduce the problem:
1. go  to https://sketchfab.com/models/6f2e7a64069242f8b205aff795073434/embed?autostart=1&stats=1&drs=0
2. see fps go above 60
3. do a performance profile to see that requestanimationFrame are called twice by frame

What is the expected behavior?
One requestAnimationFrame per frame

What went wrong?
- We get two requestAnimationFrame per frame.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 70.0.3538.77  Channel: stable
OS Version: 10.0
Flash Version: 

We only get that behaviour on sketchfab.com, not on any other domain with the exact same code (staging server has only one requestAnimationFrame per frame).

We deduce it might be related to the fact it's a domain we enabled the "webvr token" with
 
two-raf-one-frame.jpg
726 KB View Download
Cc: klausw@chromium.org bajones@chromium.org
Components: Blink>WebXR
Owner: billorr@chromium.org
Status: Assigned (was: Unconfirmed)
Could one of the WebXR folks please triage this perhaps in conjunction with Paul from Sketchfab? Thanks.

paul@sketchfab.com, Did you set webvr or webxr flags when testing this, or were you running without flags?
We tried with a browser with all webvr and webxr flags disabled. 
(default settings)
We also tried with every webxr/webvr flags enabled and we still didn't have the issue on the other dev server (no token).

Small note: the model posted above takes ages to load because of long shader compilation, but the issue is reproducible on every model (here's a lighter one 
https://sketchfab.com/models/63b73dcf59de461cb5a5a6adc8a557ff/embed?autostart=1&stats=1&drs=0)
We reproduce the bug on firefox too, so you probably shouldn't investigate the issue at this moment, sorry for the wrong blame :)
It's  definitely on our side.
 
You can safely ignore this bug report 
Please accept my appologies.
Status: WontFix (was: Assigned)
Thanks for confirming. Closing.

Sign in to add a comment