random `WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost` on a relatively simple page.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description:
- A-Frame Version: 1.2.0
- Platform / Device: Quest 2
- Reproducible Code Snippet or URL: https://8-2021-naf.glitch.me/tracked-controllers.html
Page crashes, especially if attempting to enter VR as soon as possible. The log warning before the crash is just
WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost
three.js:18936 THREE.WebGLRenderer: Context Lost.
No stack trace, no other clues.
I haven't investigated pulling pieces out yet, will remove environment and see if that fixes it. Issue seems somewhat intermittent at this point, but will update here if I get to the bottom of it.
This page features hand-controls, environment 1.2.0, and networked A-Frame latest. Will pull those pieces out and see which fixes it. Just putting this here for now partially as a reminder to me to investigate later.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the tracked-controllers.html reproduction URL on a Quest 2 and observe the WebGL context-loss warning when entering VR quickly. Compare the page with the listed hand-controls, environment 1.2.0, and networked A-Frame components removed one at a time. Done means identifying a reliable trigger and a clear fix or actionable minimal reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, three.js
- Domain
- computer-graphics, web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100