Jump to content
rich22

[1.7.0.293] Crashes on closing a file before "Loading" has completed (i.e. reached 100%)

Recommended Posts

Posted (edited)

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

 

 

Edited by rich22
New understanding of the problem, different enough to warrant a change in title and a new more accurate description

Share this post


Link to post
Share on other sites

Hello @rich22,
welcome to this forum.
I can not confirm crash described by you.
I use several Pentax cameras from the K10 to K3, and opened all PEF files without any problems.
Try converting the PEF files to DNG format,and see what happens then.

Cheers


Affinity Photo 1.7.3.481 :   Affinity Photo-Beta 1.8.0.486   :    Affinity Designer 1.7.3.481:  Affinity Designer-Beta 1.8.0.486:

Affinity Publisher-Beta 1.7.3.475:   Affinity Publisher 1.7.3.481:    Windows 10 Pro  (Version  1903 Build 18362.295)

 

Share this post


Link to post
Share on other sites

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)

Share this post


Link to post
Share on other sites

Unlikely to be an installation problem, but you might try pressing and holding Ctrl while you start the program. Once the dialog box comes up (may be hidden behind other windows), leave the first 3 boxes checked and then press the Clear Defaults button. That might help.

By the way, your .pef file worked just fine for me when I followed your directions. No crash.


-- Walt

Windows 10 Home, version 1903 (18362.356), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.486 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.486 Beta  / Affinity Publisher 1.7.3.481 and 1.7.3.475 Beta

Share this post


Link to post
Share on other sites

I would try the suggestion of walt.farrell.
Very strange, the crash with dng files.
Note, if affinity photos is reset to default,  all user settings are lost.

 

Cheers


Affinity Photo 1.7.3.481 :   Affinity Photo-Beta 1.8.0.486   :    Affinity Designer 1.7.3.481:  Affinity Designer-Beta 1.8.0.486:

Affinity Publisher-Beta 1.7.3.475:   Affinity Publisher 1.7.3.481:    Windows 10 Pro  (Version  1903 Build 18362.295)

 

Share this post


Link to post
Share on other sites

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.

 

Share this post


Link to post
Share on other sites

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

 

 

 

Share this post


Link to post
Share on other sites

Hi @rich22,

Sorry for the delayed reply. 

My "loading" finishes at the same time as the "save document as..." progress bar, so I cannot replicate the crash. Any chance you can send us a screen recording of this in action?

Thanks

Gabe. 

Share this post


Link to post
Share on other sites

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.)

 

Share this post


Link to post
Share on other sites

Hey rich22,

Gabe has asked myself and a few others to try this internally and we are really struggling to reproduce it.

Would you mind providing us with the following:

  1. Your operating system
  2. Specification of the machine you are using
  3. Save location (HDD, USB stick, Network drive etc.)
  4. The file you are using. Here is a private Dropbox link that only QA/Dev will have access to - https://www.dropbox.com/request/0LwuHnuNPYlLhlBPdret

We can then attempt to more closely match your environment and hopefully reproduce the crash.

Thanks! :) 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Hey rich22,

I can consistently get this to crash now. It seems it has nothing to do with your images or specs. The key is definitely the network drive. I can get this recipe over to the developers now. Thanks so much :) 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.