(06-09-2015, 06:03 PM)sbozkus Wrote: Petr, Gary's response was for me.

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.

(06-09-2015, 06:21 PM)Petr Wrote: Gary,
is not it true that you wrote me how to download and install a 32-bit version. It is also not true that I use version 12 of last year. In fact, you never wrote to me. All emails Angelique wrote.

I use version 12 of March this year. Before that I used Version 11 Version 12 has worked without error one month. Since April, the program does not work at all.

After several reinstallation, I had to check my laptop to an authorized service center. The notebook is fine with the current driver.

I like to try the 32-bit version. Please write the address to download.

Thanks. Peter

(06-10-2015, 09:31 AM)Gary Wrote:

(06-09-2015, 06:03 PM)sbozkus Wrote: Petr, Gary's response was for me.

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.

Hi Sbozkus

Yes and sorry I've got mixed up when Petr was replying to my reply to you. The problem is the code that runs during standalone for saving files is exactly the same code as runs when in the plug-in so I don't see how it could be due to a different way we are handling memory. In fact when run as a plug-in there is generally less memory available to Portrait Pro due to Photoshop using many resources including memory. When run as a plug-in the Portrait Pro code always saves a TIFF file. Can you try that to see if it works?

thanks
Gary

(06-11-2015, 10:08 PM)sbozkus Wrote: When it fails; it'll fail for any save option (tiff or jpg or png). At that time your standalone SW will freeze till you close it down with it's "X" corner.
If you restart and try again; it'll also fail.

(06-11-2015, 11:07 PM)Gary Wrote:

(06-11-2015, 10:08 PM)sbozkus Wrote: When it fails; it'll fail for any save option (tiff or jpg or png). At that time your standalone SW will freeze till you close it down with it's "X" corner.
If you restart and try again; it'll also fail.

When it is going to fail, can you use "save session" and send me the resulting session file. Use dropbox or one of the many web sites for sending large files and then please send me a private message in this forum with a link to the file. If we can reproduce this problem then we will be in a much better position to fix it.
thanks
Gary

(06-14-2015, 02:49 AM)sbozkus Wrote: Of course; save induced crash starts right away on x64 version. The interesting thing is; it even crashes on "save session" request. So it can not do any kind of save at all.
I sent you Windows event file content via private email.
Interestingly, the last binary bytes (as it crashes) reads: C.r.o.s.s.-.t.h.r.e.a.d..D.e.a.d.l.o.c.k...
So it tells you why it's dying. Hope you can find the killer!

(06-15-2015, 04:10 PM)sbozkus Wrote: It happens immediately as you click on (one of 3) save options. You don't see any change on screen (even your requested "save file name" popup window doesn't come). It just freezes right there and then. For about 4 seconds it doesn't even respond to "X" close corner button. After 4 seconds top window bar says "(not responding)". Then you can close it by "X" corner button. After that you can relaunch the SW but it'll crash exactly the same at same point.
Interesting enough; it decided to work today when I turned on my PC. It's luck of the day. Probably if I reboot now once again it'll decide not to work.
So you don't have any utility to trace / capture it's behaviour step by step? If you have so; you can send it to me. I can try to capture it's log file and send you details. Otherwise, looks like it'll just remain the same since you can't replicate it.