Duh! Poser 5 has a 4MB memory leak per render. Add that to poor, really poor memory management, and many other memory leaks, and ... Ergo, the only real way to stop P5 running out of memory is to not use it. Failing that use it as little as possible between reboots. (Per my definition that means the program doesn't work worth a , but many will jump in to says 'tis wonderful.) I've not had it crash on me (excluding Interlok triggered ones) - even on 5.0 pre-SR1. And my memory configuration has always been limited to < 2GB. E.g. 1GB real, 960MB virtual. A coincidence? Maybe, but I've optimized that virtual memory size for another application, so I've not tried messing with it. Plus I gave up using P5 for anything real some time back because it behaves just like (read 'as badly as') Poser 4 does with 5+ clothed complex figures in it, except it all occurs in P5 with just the one simple nude figure loaded! An EVM just waiting for SR4, or is it 5? , or maybe 6? - but holding out little hope of a satisfactory outcome, ever.