One problem is that we don't really know what or how Poser is managing memory internally, so it would be hard to pin it down to some particular operation.  Having said that, I'll continue to trippl-check my reference tracking, because the C code can indeed cause leaks.

My current understanding of the Python side of things (after working on the .pyd and being exposed to what's going on under the hood) though is that there really isn't anything the script itself can do to cause leaks.

But if you can boil it down to a simple test that seems to show repeatable results leaking relatively large amounts of memory, that would be worth looking into.

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.