Let's say you have a sketch that brutally abuses texturing in OpenGL, by completely redrawing an offscreen PGraphics each frame, then using it as a texture, forcing all of the entailed conversion work. (that is, without any glTexSub* -type hackery)

In current 1.0 such code seems to leak texture memory.  Depending on texture dimensions it'll run out of memory after some number of frames and bail.

In the olden days of beta you could avoid that particular leak by explicitly coding something like "pimage.cache = null;", then the destructor would release the texture id and clean up after itself, then recreate the OpenGL texture from scratch.  (the brutal abuse)

In 1.0 it seems removeCache() is the new replacement, but as it's not documented, am wondering how to use it, or if I'm even on the right track.  Do I just pass it a reference to "g" (meaning the onscreen OpenGL renderer)?  Or is this leak entirely unexpected and i should be reporting a bug instead?

thx