I just discovered something interesting.  I ran C5 and did a fairly involved render, with no poser imports.  I have a memory manager that keeps track of memory usage by applications.  During the render, C5 was stuffing about 1.2GB of data into the swap file.  In addition to about a gig of normal ram.  After the render, C5 did NOT clean up the page file area and left a ton in normal RAM.  When I exited the program, C5 still did not clean up after itself properly, and left about 400MB in page file, and 300MB in RAM, all of it highly fragmented.  I think this is half the problem with memory allocation errors.  The program simply isn't cleaning up after it completes tasks and then tries to use the same RAM.  I restarted C5 without cleaning the memory manually and the next render I did, sure enough, memory allocation error.  I closed C5 again, ran my memory optimizer, and then back to C5, and then it would render.  I am not sure if this is a windows problem or a C5 issue, but it's definitely not good.

 

Quote - Hi ren-mem and bionic buddy. I have exactly the same memory allocation error on my mac when I tried to render a PZ3 of a classroom with about 12 fully dressed and posed mil figures. It just kept crashing or giving me that memory allocation error. I submitted a bug report. O kay it was a huge file about 650 megabytes, but I have a very good computer and 5 gig of ram. I thought it would work. It almost worked until I added an apollo. that seemed to be the last straw. And no, it wasn't because he was apollo, as it happened after that even when I removed him. I also had files not opening again at times. Very sad. I had to render it by making several figures invisible at a time, rendering multiple times, then putting it all together in photoshop. Love esther PS seemed to happen the most when I used the toon renderer.