Proof that GLTFLoader does not free memory in Safari that it frees in Chrome

[manthrax]

Ohh I see its an explicit fallback.

Related (?):

Safari memory leak when scene dipose and rebuid serval times

I have created a scene using THREEJS that loads GLTF files and image-format tile maps. When I repeatedly destroy and rebuild the scene(ensuring that each destruction removes DOM nodes and all relevant THREEJS objects), I notice that the memory keeps increasing in the Safari browser, but the same code performs normally in the Chrome browser. I have ensured that I properly dispose of all relevant resources when destroying the scene. [image] [image] The following is the core code of my destruct…