aframevr / aframevr/aframe

Hololens fails to exitVR successfully

Open
#3,881 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
17.6k
Forks
4.4k
PR merge metrics
No merged PRs in 30d

Description

Description:

Given I am using a Hololens in immersive mode,
When I leave the immersive mode,
Then the aframe stops rendering (the browser window only display a white background and not the scene).

The reason the rendering is stops is due to an error being thrown within a component's tick. I haven't been able to track down the component. This happens with a blank scene.

The error is as follows;

TypeError: Unable to get property 'pressed' of undefined or null reference at tick (eval code:65:5) at tick.value (https://server/aframe/aframe-master.js:73647:11) at render.value (https:/server/aframe/aframe-master.js:73695:31) at bound (https:/server/aframe/aframe-master.js:77038:7) at animationLoop (https://server/aframe/aframe-master.js:27442:4)

As an aside, it would be great if component and system ticks were wrapped within a try catch. The catch could log the error via console.error and provide information of which component was being rendered rather than throwing and stopping the rendering.

  • A-Frame Version: 0.8.2
  • Platform / Device: Hololens
  • Reproducible Code Snippet or URL: Any example

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the blank-scene failure on a HoloLens by entering and leaving immersive mode, then inspect the component or system tick shown in the aframe-master.js stack trace. The work is done when exiting immersive mode no longer stops rendering and the scene remains visible; the requested tick error logging is an additional consideration.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
ar-vr-xr, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.