Well Poser crashed in the middle of working with the morphing tool. 

So I'm wondering if there is a way to stay  on top of the memory usage and if there is a way to recover from a situation like this... this will be for Poser 11. 

I know there are limitations for the older Poser versions before 12 but there must have been some brilliant person that figured out a way to get out bad situations like this. 

You know, you get to working and you don't forget to save and then this happens sort of situation!

Thanks for any tips, tricks and help! 

Richard 

If you are in the middle of a may-be-long session of a lot of modifications, I suggest that you first save your project, so that Poser has a file to save regularly, using its auto-save function:

Ah, of course, Auto Save.  Thank you! 

What does the Number of Versions refer to?  Seconds and Minutes seems pretty self explanatory but that other is a bit confusing. 

I suppose that it only keeps the defined number of old versions: the oldest are progressively deleted...
It's a kind of balance between "how long I'd like to return in the past of my project" and the place it eats on a disk: myy biggest one is 2Gb, hold 13 vic4 (plus that hairs, the little bikinis) and a swimming pool. So if you count the current scene plus 3 olds plus the first copy it creates, that's 10Gb that will remain on the hard disk, till you delete them.
Actually, my Poser12 gallery has 173 folders, not to count many sub-folders, with a lot of autosave sub-sub-folders, some housekeeping is needed from time to time

Ah, makes sense.  Thanks again! 

You're welcome

If you are in the middle of a may-be-long session of a lot of modifications, I suggest that you first save your project, so that Poser has a file to save regularly, using its auto-save function:

I've been tracking this problem for quite a while. Not a solution but a possible work-around is when you get the out-of-memory error, before clicking the OK button releasing the warning, open task manager, expand the Poser entry there and right click/end task the offending CCF node, the one that shows excessive memory usage.(no problem indicated here even though it says poser not responding/ it always says Poser not responding on my system...) .. You can then proceed as if nothing happened, ending that CCF node seems to have no effect on current work in progress(at least in my experience)... good luck

I did investigate that area before I clicked the OK dismiss button but I don't think I knew what I was looking for so gave up!  Thanks so much

This is what it actually looks like... I didn't get an OOM error, but I noticed a lag so I checked... 45gb+ and I wasn't doing much of anything. If I hadn't killed that node it would have eaten up all 64gb pretty quickly. Clicked end task on that node and returned to work with no issue.... Strange days indeed.

Can some please explain how or why that last post is so long?

Can some please explain how or why that last post is so long?

Thank you Red.