Yes, I've seen the "successive render crash syndrome" too.

I've gotten in the habit of exiting & re-starting Poser after one (1) heavy-duty render. Several simple, non-demanding renders in a row are usually OK. But one large final render eats up your PC's system resources -- and it doesn't let go of them afterwards.

In fact, doing more than one large render can then require a cold PC re-boot in order to clear up the system memory.

But this phenomenon isn't totally unprecedented. I've seen many programs besides Poser have exactly the same sort of terminate-and-stay-resident RAM-eating effect.

Something To Do At 3:00AM