search

aframevr / aframe

:a: Web framework for building virtual reality experiences.
https://aframe.io/
MIT License
16.69k stars 3.98k forks source link

a-scene memory leak on chrome #4899

Open Dirk-27 opened 3 years ago

Dirk-27 commented 3 years ago

Description:

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.

Benjy763 commented 2 years ago

Hi, I also have a big problem with chrome about memory. With Firefox it is fine, but with chrome the memory increases very quickly, it is more than 5 times the memory allocated on FF. There is a thread here https://github.com/aframevr/aframe/issues/3137 But this is a problem relative to chrome.

Hope you'll find a solution, thanks again !

dmarcos commented 2 years ago

There's a proposed solution here https://github.com/aframevr/aframe/issues/3137#issuecomment-990201997

Dirk-27 commented 2 years ago

Right. Only for clarification: This issue here (#4899) exists independent from models in the scene.

dmarcos commented 2 years ago

Any ideas why the behavior is different between Firefox and Chrome?

Dirk-27 commented 2 years ago

No. I think it is webgl related. Interesting is: 'The amount of memory used depends on the size of the browser window.' So the bug has perhaps to do with the use of some graphic buffers?

I found a chrome issue that fits to this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=811220

dmarcos commented 2 years ago

Thanks. I leave this opened as a reference