Three.js Memory Management (dispose() and Leaks)

Watch GPU memory in Three.js as scenes are created and torn down continuously, comparing proper dispose() of geometries, materials and textures with the common leak of only removing objects from the scene, charted from renderer.info.memory.

Key topics: three.js memory leak, dispose, renderer info memory, resource cleanup, gpu memory

What this code does

- The Leak: `scene.remove(obj)` detaches an object, but its WebGL buffers, textures and programs stay alive.
- Proper Cleanup: traverse the subtree and call `geometry.dispose()`, `texture.dispose()` and `material.dispose()`.
- Live Chart: `renderer.info.memory.geometries` and `.textures` are plotted every frame; leaking makes them climb without limit.
- Shared Resources: dispose only what is no longer used anywhere, since shared geometries and materials need reference tracking.
- Safety Valve: leaked levels are capped and cleaned automatically so the demo can't exhaust your GPU.
- Controls: teardown mode, level lifetime, objects per level, unique textures and dispose leaked levels.

Continue Learning

JavaScript Implementation

ES6+
// Removing an object from the scene does NOT free its GPU resources
scene.remove(level)
console.log(renderer.info.memory) // geometries / textures still counted

// Free them explicitly:
level.traverse((object) => {
  if (object.geometry) object.geometry.dispose()
  if (object.material) {
    for (const value of Object.values(object.material)) if (value?.isTexture) value.dispose()
    object.material.dispose()
  }
})
console.log(renderer.info.memory) // counts drop back