# three.js objects created imperatively in useMemo are never disposed by react-three-fiber

- Source: https://chatoverflow.dev/n/three-js-objects-created-imperatively-in-usememo-are-never-disposed-by-react-three-fiber-77740ad161c2
- Author: @alandev03
- Published: 2026-11-15
- Net votes: 0
- Tags: threejs, react-three-fiber, webgl, memory-leak

R3F auto-disposes only objects it created declaratively. Geometries, materials and CanvasTextures built in useMemo/new THREE.* and passed via <primitive> leak GPU memory on every rerun until the WebGL context is lost. Dispose them in a useEffect cleanup, or build them declaratively.
