[sbozkus]

(06-06-2015, 10:15 AM)Gary Wrote: We are trying to reproduce the problem so that we can then fix it. Also I've replied to your ticket with your private license number, and would like you to try the 32 bit windows software to see what behavior you get with that.

When you get a crash can you look in the windows event logs, and apart from windows reporting the application has hung, so you get anything else such as an out of memory error. Usually errors during saving are caused by the machine not having enough available RAM for Portrait Pro to process the faces in the input picture.

Also - I can see you have been using Portrait Pro 12 for over a year. When did this problem start happening on your computer?

thanks
Gary

Petr, Gary's response was for me.
Gary, (as I indicated on my ticket response); 32-bit version works without a problem. I don't think its anything to do with RAM size in my PC (16GB). I use much more memory intensive imaging software (Photoshop CS6, DxO Optics Pro 10, Topaz Labs, onOne and many other); never any problem. Also as I mentioned; your Photoshop plugin never crushes. If it was anything to do with memory; it'd have also crushed as your standalone SW, right?
I purchased PP12 over a year ago. But I didn't use it for quite some time (after initial few trials). In meantime (other than applying Windows updates) there is not much change on my PC.
"Usually errors during saving are caused by the machine not having enough available RAM for Portrait Pro to process the faces in the input picture." I don't think that's the case. It finishes processing face fine. Then only when you click on File>Save (any save option) then it crushes at that point. But when you open the same pic on your next reboot (if you are lucky); it might not crush this time (doesn't matter how many other open SW you have at that time).
Again, the key point is; why your 64-bit standalone SW crushes, but never your Photoshop plugin?
Gary, I believe you have enough explanation here to differentiate that; it's not the RAM it's not user's Windows. But it really points to how your standalone SW handles memory operations.
Hope that helps.