WebGL memory management puzzlers

[trusktr]

Are you making sure you clean things up? See here:

When to dispose: How to completely clean up a Three.js scene

Continuing the discussion from API Documentation: If we are completely done wanting to have a Three.js scene exist in an application (f.e., suppose we have a single page application where the page was rendering a Three.js scene, and we’ve switched to another view and we no longer need to render any Three.js scene), how do we properly and completely clean the scene up so that no traces of it left behind in memory? Here’s some things I can think of: Call dispose() on all geometries Call dispos…

The need for a "How to clean things up" section of the docs

I’ve opened a couple threads on cleaning things up: How to completely clean up a Three.js scene from a web app once the scene is no longer needed Disposing OBJLoader and MTLLoader But my thought is that in general the Three.js docs need a “How to clean things up” section, as it isn’t totally clear when/how to do it, and when not to do it. It’s easy to miss it, and perhaps leak. So, just jotting down some ideas: In this section, it’d be nice if it can talk about patterns (f.e. when to clean …

Basically make sure you clean up any objects that you are done with. Whatever you discover, it would be great if you add your findings to those discussions so it may help others too.