a-scene memory leak on chrome
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 and master
- Platform / Device: Chrome Desktop (Version 92.0.4515.131 (64-Bit))
- Reproducible Code Snippet or URL: https://jsfiddle.net/neomatt/4jw6xyhe/8/
Creating an a-scene allocates memory that is not released. This behaviour can be observed in the chrome browser (not in firefox). The amount of memory used depends on the size of the browser window. The memory used seems to be associated with the browser window even after removing the a-scene tag. So if you increase the size of the window after running the jsfiddle script, you can observe a higher memory usage in Chrome.
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 memory behavior in the linked JSFiddle using Chrome Desktop and compare it with Firefox. Investigate what remains allocated after removing the a-scene element, including the effect of changing the browser window size. Done means the reproducible scene no longer retains the reported window-dependent memory in Chrome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100