[Affected versions]: Fx 55.0.10 [Affected platforms]: Windows 10 x64 [Steps to reproduce]: 1.Launch Fx and go to https://aframe.io/a-blast/ . 2. Click from the page the VR button to start the demo. 3. Play the game. [Expected result]: The browser assures a smooth play. [Actual result]: The game freezes in the VR device after a short while. [Regression range]: This is not a regression as this feature is new. [Additional notes]: a. The browser displays a smooth image. b. Sometimes before the freeze the VR displays jerky moves. c. Also reproducible with: https://aframe.io/examples/showcase/videosphere/

(In reply to Cristian Comorasu [:CristiComo] from comment #0) > [Affected versions]: > Fx 55.0.10 > > [Affected platforms]: > Windows 10 x64 > > [Steps to reproduce]: > 1.Launch Fx and go to https://aframe.io/a-blast/ . > 2. Click from the page the VR button to start the demo. > 3. Play the game. > > [Expected result]: > The browser assures a smooth play. > > [Actual result]: > The game freezes in the VR device after a short while. > > [Regression range]: > This is not a regression as this feature is new. > > [Additional notes]: > a. The browser displays a smooth image. > b. Sometimes before the freeze the VR displays jerky moves. > c. Also reproducible with: https://aframe.io/examples/showcase/videosphere/ Could you please provide more details? - What headset was being used (ie. Oculus or HTC Vive?) - How long did you wait before it froze? - Did refreshing the page correct it? Thanks!

We have uplifted a number of stability fixes to Beta in the past weeks. Please advise if this problem is still occurring.

Hello Kip! I used Oculus Rift, to fix this issue the user must restart the browser. The time until the freeze occurs is not constant, however an average would be 7 minutes. Refreshing the page causes the VR device to remain in a closed status. Are the stability fixes available in Fx 55.0b12? Thank you!

@larsberg mentioned that this may be a WebAudio related leak. IMHO, this should not block WebVR in 55, but should be investigated further.

I re-tested using Fx 55.0b13 and the issue is no longer reproducible. Cheers!

Marking as fixed, as per Comment 5.

I re-verified using Fx 57.0b5 and Fx 58.0a1 (build ID: 20171004100049) on Windows 10 x64 and I can confirm this issue is fixed.