Frequently Dispose AssetContainer Causes Memory Leak

[RavenLee]

Hi sebavan,

Thank you for your reply. Sure it may take longer than 100ms since it is a async function. I tried 1000ms which loading process can be finished and it got slower increase.

I found this one may relate to this issue:

I discovered the worst and most insidious memory leak in BabylonJS history

In my BabylonJS project, I used the queryObjects(Promise) command and found that several thousand Promise objects were leaking memory.As shown in the figure below. [修复前对象泄漏] [修复前内存占用] I tried to analyze the memory leak Promise objects. I guessed it was GLTF loading module, so I tried to modify the source code of the module, and it worked.The culprit from GLTFFileLoader. prototype. loadAssetContainerAsync, here is my modified code. GLTFFileLoader.prototype.loadAssetContainerAsync = function …

Other observations:

1. If I use scene.onDisposeObservable.clear() after disposing assetContainer, the empty assetcontainer class will be cleaned.
   
   
2. using chained Promise and returns Promise(assetcontainer) causes faster memory increase than just return the assetcontainer itself.