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

**URL:** <https://discourse.threejs.org/t/proof-that-gltfloader-does-not-free-memory-in-safari-that-it-frees-in-chrome/75201>\
**Category:** Discussion\
**Created:** [December 15, 2024, 12:56am UTC](https://discourse.threejs.org/t/proof-that-gltfloader-does-not-free-memory-in-safari-that-it-frees-in-chrome/75201 "2024-12-15T00:56:38Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![manthrax](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/manthrax/32/2596_2.png) [@manthrax](https://discourse.threejs.org/u/manthrax)\
**Post date:** [December 15, 2024, 5:19pm UTC](https://discourse.threejs.org/t/proof-that-gltfloader-does-not-free-memory-in-safari-that-it-frees-in-chrome/75201/10 "2024-12-15T17:19:48Z")

</div>

Ohh I see its an explicit fallback.

Related (?):

> [@Safari memory leak when scene dipose and rebuid serval times](https://discourse.threejs.org/t/safari-memory-leak-when-scene-dipose-and-rebuid-serval-times/59014):
>
> 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. The following is the core code of my destruct…

😃

---

_[View the full topic](https://discourse.threejs.org/t/proof-that-gltfloader-does-not-free-memory-in-safari-that-it-frees-in-chrome/75201)._