GPU Resource Disposal Limits in Complex Scene Graphs

Manual Memory Management in Three.js

Three.js requires explicit resource management for assets resident on the GPU. While JavaScript handles CPU-side memory via garbage collection, GPU-resident data such as BufferGeometry, Material, and Texture objects must be manually released using the .dispose() method.

Resource Orphanage Constraints

Removing a mesh from the scene graph via scene.remove() does not trigger the disposal of its associated geometry or materials. In complex applications where objects are frequently created and destroyed, this behavior can lead to steady VRAM growth if every referenced asset is not tracked and disposed of individually.

There is currently no built-in mechanism within the WebGLRenderer to automatically track and purge all orphaned GPU resources associated with a removed object hierarchy.

• How can a developer reliably identify all leaked GPU buffers without manually mapping every material-texture relationship?
• Is there a documented strategy to implement a centralized resource tracker that ensures .dispose() is called on all dependencies when a parent object is removed?