I also using a webkit profiling tool to check the trend on my iphone12, it looks like the following graph.
Both physical memory and memory go up stably like going upstairs and the avaliable memory drops.
Sure I will put the code in zip file on the playground. While for the repro in zip file (above one) I load the glb file locally, but on playground I may use a remote one, which may introduce the request time and network problem. So I wonder if there is some approach load the glb in playground locally?
Thank you for your cencern for this issue. I am struggling with providing a proper online repro on this issue. While fortunnately I found some clues, if you have a look at the zip file and run it by a local server. if I QueryObject(AssetContainer) there are some AssetContainer empty left.
And looking at the code, I noticed there’s both a call to addAllToScene AND instantiateModelsToScene, the second of which DOES duplicate the skeletons, as per documentation: AssetContainer | Babylon.js Documentation (babylonjs.com). After properly disposing of these skeletons by using the returned skeletons property returned by instantiateModelsToScene, the memory usage doesn’t grow anymore.