Dropped frames after mousedown on Chrome/Bing on scenes with large number of nested entities
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
- A-Frame Version: 1.2.0
- Platform / Device: Chrome/Bing
I am running into a problem where a large number of nested objects causes Chrome and Bing to drop frames proportionally to the number of nested objects whenever the scene is clicked on (for instance to look around with the camera). This does not occur in Firefox, or when the aframe inspector is open in Chrome/Bing ( Able to move the camera, click on entities and interreact as normal )
The dropped frames seem to happen after/while it updates the layer tree.
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 by reproducing the frame drops in the reported A-Frame 1.2.0 scene with many nested entities after mousedown in Chrome/Bing, then compare Firefox and Chrome with the A-Frame inspector open. Trace the layer-tree update associated with the click and verify that the affected browsers maintain frame performance without changing scene interaction behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100