rich22

Thanks for the quick answer! I think I'll give the MSI installer version a try.

I occasionally use Faststone Viewer to quickly scan through images, and occasionally perform some preliminary edits just to 'check things out'. Today I tried adding the Photo 2 executable to Faststone so that I can easily invoke it when I want to do an edit from the viewer. Unfortunately, that simple task no longer works, and it has something to do with this "new" way Photo 2 is installed. The only reason I know this is that If I try to invoke the executable directly, it doesn't work! The failure seemingly has to do with permissions. I started looking at security settings, but realized it would be foolish to start mucking with that as I'd probably render my system unusable. Is there any way to make this installation work in a more "normal", expected manner? (I'm on Windows 10.)

You're welcome. I'm glad you were able to reproduce it!

Hi Chris - Sure - here's the information: 1. Windows 10 Home, version 1809, build 17763 2. I've attached two files with the output of the System Information tool, one for the overall system and one for the display adapter. It's an Asus M32CD, dual-core i3 @ 3.7ghz, 16gb RAM, with a GeForce GT710 display adapter. 3. The save location is to a Synology DS216j NAS system. BUT -- your question got me thinking, so I tried the steps in my video when saving to the local hard drive. In that case, the "Loading %" step is so fast there's no time (or need) to press Ctl-W! So if I had been saving locally all along, I don't think I'd have ever seen this happen. 4. I uploaded the file to Dropbox. Also, please note that this happens with any PEF, NEF (from a Nikon D3300) and DNG files that I've tried. (And one more thing - in the current production version this doesn't happen at all. There's no "Loading %" displayed at all after the file save progress bar is done.) System Info.xls Display Adapter Info.xls

Hi Gabe - No problem. I've attached a video file showing the steps that lead to the crash. The point in the video where you see the "Loading NN%" display freeze is the point at which I pressed "Ctl W". Then you can see that display freeze, and about a second after it freezes, the program crashes. (Video has been updated.) Affinity Beta 293 Ctl W Crash.mp4

Yes. When I said "Clipboard History setting that causes the crash", I simply meant the position of the setting, and wasn't speculating about which actual program is crashing.

It's the "Clipboard History" setting that causes the crash. Go to "Settings" / "Clipboard" - with history on, AP crashes. With it off, it doesn't. But I agree - it shouldn't crash in either case!

I did some more testing with this, and it looks like the crash is related to when Ctl-W is pressed. After the .afphoto file is saved, the program displays "Loading" and an increasing percentage figure. If I press Ctl-W while that percentage is still increasing, that's when the program crashes. (The increasing percentage display freezes for a couple of seconds at whatever value it's reached, and then the crash happens.) Whereas, if I wait for the percentage to get to 100, and then press Ctl-W, it doesn't crash. Note that the crash happens even if I do nothing to the photo. Pressing Ctl-W while the "displayed percentage" is increasing is sufficient to cause the crash. (Interestingly, the current production version - 1.6.5.135 - doesn't utilize that increasing percentage display. It only has the "Save document as" progress bar, and it seems that "Ctl-W" is ignored while that progress bar is being displayed.) So now, the steps to create the crash are: 1. Open a raw file (PEF / NEF / DNG in my case) 2. Make no changes 3. Click on "Develop" 4. Make no changes 5. Save the file to .afphoto format 6. When the program is finished displaying the "Save document as" progress bar, press "Ctl-W" while the increasing percentage is being displayed (above image, to left) 7. The percentage display freezes, and roughly two seconds later, the program crashes

Thanks for the suggestion. Unfortunately, the program still crashes. So I tried checking all the boxes and then pressing "Clear", and it still crashes. Then I tried uninstalling and reinstalling the beta, and still no joy.

Good suggestion. I tried with DNG, and also with NEF files from a D3300. Same thing happens. Yet I've used the previous versions of the beta without this problem occurring. And - this doesn't happen with the current production version 1.6.5.135. Could it be an installation issue? I didn't uninstall the previous beta before installing this latest one. (Running Windows 10 Home version 1809 build 17763.437)

I've edited this thread because the understanding of the problem has changed. I originally believed it had to do with the type of raw file being edited. On further testing, I found that there's a new "Loading" display after a file is saved to .afphoto format. If the file is closed using Ctl-W or by clicking the "X" before that loading reaches 100%, the program crashes. The steps to create this problem are (these are also in the current last post in this thread): 1. Open a raw file (PEF / NEF / DNG in my case) 2. Make no changes 3. Click on "Develop" 4. Make no changes 5. Save the file to .afphoto format 6. When the program is finished displaying the "Save document as" progress bar, press "Ctl-W" while the increasing percentage is being displayed in the "Loading" line above the image, to the left 7. The percentage display freezes, and roughly two seconds later, the program crashes