Memory not freed when updating material src
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
This issue was closed as resolved in 2017 but it seems still present. There should be an easy way to update the src of a material and clear the memory of the old material. Simply updating the src parameter leads to continuously increasing memory utilization as shown by the example below.
- A-Frame Version: 1.4.0
- Platform / Device: Firefox 108.0.1 on Windows
- Reproducible Code Snippet or URL: https://jsfiddle.net/0kxzfjep/
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 reproducible jsfiddle.net example and compare the behavior with the earlier issue #2640. Trace how updating a material's src handles the previous material and verify the result by repeatedly changing src while monitoring memory. Done means old material memory is released instead of continuously increasing utilization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100