Limits of renderer.info.memory when distinguishing leaked from cached Three.js resources
Three.js requires explicit dispose() calls on geometries, materials, and textures to release GPU memory, yet renderer.info.memory reports only aggregate geometry and texture counts. When meshes share geometries or textures, the library offers no ownership or reference-counting mechanism, so a rising count may reflect either a leak or an intentional cache. Af
threejs