What strikes me as bizarre is how the memory leak continued through all of Poser 6's SR's. It was never caught, never addressed. It was non-existent for me in the "out of the box" installation, but reared its ugly head with the first SR for Poser 7. Someone apparently screwed up somewhere. I don't think it has to do with a system config, but how the program itself addresses memory and memory usage. I can open a scene in 3D Studio Max that has close to a million polys, and not get the same error. If it were a configuration problem, one would think that other 3D apps would get a lil bonky. Not so with my system. Its stable, unless I open up a 4gb HD Video file, then it slows down to a crawl.

Makes ya wonder.