I just added 10 V4's to the 10 M4's, fully loaded with Morphs ++, as well as wearing 10 pairs of shorts, also with Morphs ++ in them. So 30 figures total. Oh, and they had gigantic 4K by 4K textures on them. Looking at Task Manager, I had 20 MB of memory left out of the 2 GB. Poser then crashed when I tried to render.

So, yes, it crashes when you run out of memory. 

As for memory leaks, there are certain kinds that are avoidable, and other kinds that are not. They aren't really leaks. It has to do with how memory gets carved up. Over time, big chunks get cut up to little chunks to use for smaller things. Then when these are returned, but not all can be returned because some objects are still in use, you end up with no more big chunks. Textures have to be loaded in big chunks. So Poser has to allocate a new big chunk. After a few iterations of this, there's no more room to allocate a big chunk, even though there are lots of little chunks available.

This is why enterprise servers are periodically rebooted, so that memory can be released.

If you're hitting this situation, it may help to render in a separate process. That way, the renderer gets its own memory, and when the render is finished, all of it is released as one big chunk. Rendering in a separate process is the way to avoid memory fragmentation. That's why rendering in a separate process was introduced.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)