Hmm.... I wasn't trying to be controvesial, but I was trying to be simplistic (so laymen could possibly understand). I AM a systems programmer. So I know that memory handling can be difficult/awkward. It's just that there several techniques that help things considerably. Mind you, on thinking it over, one of Poser's problems must come from the fact that it's multi-platform; so what works on the PC may not work on the Mac (or vice versa). Plus they sub-contracted a lot of the work (so there was no real control over that part of the project) and improted 3rd party apps (like Firefly). Ah, well. Maybe my previous post was just me trying to show off my "superior" knowledge..... I agree that (almost) all apps suffer from memory leaks. Sometimes it is almost impossible to avoid, and with an app like Poser (especially with so much legacy code included), it wouldn't be possible without a complete re-write of the whole system, including the core. And that would be cost-prohibitive (yes, I do live in the real world). So, yes svdl, that's what I do. Save early and save often (like voting). And I save under at least a grandfather-father-son system, or else just simple sequentially named files. BTW - part of that "memory leak" is probably due to Poser's caching system (in materials, I believe, possibly elsewhere). It's a moot point as to whether that should be counted as a leak; it's deliberately retained. But then it can be argued that File->New should flush any cached stuff.. Cheers, Diolma