Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=1231338

Poser has to have some sort of memory leak, its memory management is horrible. Why would a file render perfectly using Poser 4 renderer in Poser 5 and lock up Poser in Firefly. Can somebody explain me that one? I was able to get Firefly to render the image a couple of times but every time I lock up I have to restart Windows to clean the memory and load Poser without anything else running and I might have a chance of my scene to render. I'm dealing with hefty scenes with multiple figures 10 figures tops, no Vickys 3. ----------------------------------------------------------------------------------------------------------------------- See my previous post here http://www.renderosity.com/messages.ez?Form.ShowMessage=1231338 Firefly will still lock up when rendering complicated scenes that Poser 4 has no trouble with. These scene is a little over 100 MB. Renders fine in Poser 4. With the latest SR 3 still locks up, still cannot cancel. As soon as memory use goes to 100% Poser 5 locks up, I posted this way back in the beta forum. I cannot believe stability wasn't addressed in this release. I should have know it when I didn't read anything about addressing rendering lock ups in the service release fixes. Windows 2000 SP 3 1GB 1066 Rambus memory 80 gig hard drive Pentium 4 2.53 GHZ Poser 5 SR 3 Still one frustrated user ------------------------------------------------------------------------------------------------------------------------ And please Ulik, don't think I'm screaming at you or anybody from Curious Labs that has the courage to come and try to help us but the reality is there is some really messed up code in Poser 5 that nobody has been able to straighten up yet.