Photo 1.9.2.1035 reproducible crash

[george++]

Hi,

Please watch the following video.

I can send the file if that helps

[komtur]

I have observed similar problems since installing 1.9.2. Copying and pasting a layer and trying to manipulate it sooner or later crashes the program. Usually almost immediately.

[Gabe]

Hi @george++,

Is this document specific? Can you replicate it in a new doc? Can you keep an eye on the Task Manager and see if you see any unusual activity when it crashes? Can you attach a crash report? 

 

 

[george++]

Hi Gabe,

Quote

Is this document specific? 

I really don't know. I have the sense the the previous version is more stable. This is a crash that I managed to reproduce. Some times the program crashed before but I considered it a coincidence

Quote

Can you replicate it in a new doc?

No

Quote

Can you keep an eye on the Task Manager...

There is no unusual activity when it crashes.

I've attached a crash report

2ab2bfd6-b0a1-4751-a2e7-21da8618dcb4.dmp

[Komatös]

Can you post the Hardware (CPU/GPU) you use and how much RAM is in your computer. Which Windows version is used.

[george++]

I hope the following image will help:

[gingerging]

Since updating to this version I get a crash every 5 to 10 minutes.

Not sure what you changed but the stability of this is just awful now.  Bordering on unusable.

The crashes I get are so random, but always during standard image manipulation like curves, colour balancing etc.

So frustrating, especially considering one of the big points of this update was removing bugs!

Edited April 12, 2021 by gingerging

[PeteMacca]

Versions 1.9+ are set to use hardware acceleration. If your system can't do it, it will crash.

Try updating the GPU (graphics) driver. If that doesn't work, turn OFF hardware acceleration in Preferences>>Performance.

[Uncle Mez]

is it me or i can't find this release "Photo 1.9.2.1035" on the beta channel?
is this a stable build ?

[PeteMacca]

Yes, 1.9.2.1035 is stable, and newer than the latest beta.

[Uncle Mez]

3 minutes ago, PeteMacca said:

Yes, 1.9.2.1035 is stable, and newer than the latest beta.

Thanks 
I received not the regular email about that so, i didn't knew.

[Komatös]

@george++ 

My first recommendation is to update the Intel and the Nvidia drivers.

Secondly, if you haven't already done so, disable the hardware acceleration in Affinity Photo.  In the preferences you can also set the renderer. The Nvidia 1650 should be selected here.

Since the PC only has 8 GB of RAM and a dedicated GPU, switching off the iGPU in the BIOS could also help. The iGPU then no longer uses part of the RAM. 

 

[Gabe]

That seems to crash in your nvwgf2umx.dll Which is related to GPU drivers. Have you tried what has been suggested here? (update drivers)

[Gnobelix]

11 hours ago, gingerging said:

Since updating to this version I get a crash every 5 to 10 minutes.

Not sure what you changed but the stability of this is just awful now.  Bordering on unusable.

The crashes I get are so random, but always during standard image manipulation like curves, colour balancing etc.

So frustrating, especially considering one of the big points of this update was removing bugs!

Hello @gingerging,

Welcome to the forum.

My experience is , when OpenCl is enable, there are unexpected crashes or Affinity freezes.
Is OpenCl disable, workd Affinity well, but with a loss of speed.

Try the suggestions above to resolve the problem.
I think there will be an update or a new beta in the foreseeable future. 

Cheers

[george++]

Thank you both, for the tips

The GeForce Experience reports that my driver is up to date (465.89 Release Date 03/30/2021)

It is true that if I disable the hardware acceleration in Affinity Photo the application won't crash. But it is unpleasant to degrade the performance of the Affinity Photo by setting off the hardware acceleration

 

[Komatös]

2 hours ago, george++ said:

...But it is unpleasant to degrade the performance of the Affinity Photo by setting off the hardware acceleration

However, this is the only possible way to work with the programmes at the moment. 😟

[Gnobelix]

1 hour ago, Komatös said:

However, this is the only possible way to work with the programmes at the moment. 😟

I agree

[gingerging]

Hi

Not really a fix is it.  Here is a users experience... Open. Crash.  Open a file. Crash.  Open, open a stack. Crash.  Run a stack, Crash.  Run stack, adjust curves. Crash.  Open file again, adjust balance, crash.  Adjust sharpness, crash. ... Use DSS - ok.  Use APP - ok.  Use anything else - ok.

The fix? - disable things that MIGHT make it work (not guaranteed) and will slow it down.  Maybe we'll take a look some time.

Remind me what i paid for?  Oh yes, an editing app that works!!!!!!!!!!!!!!!!!!!!!!!!!!

Rubbish, total rubbish.  Affinity, get your bloody act together, this is absolute dog $#!£.  Test your releases for pitys sake.

Get it done, its been weeks and nothing.  Sort it out and stop making excuses.

Edited April 16, 2021 by gingerging

[Patrick Connor]

Hardware acceleration is working well for thousands of users, so it is on by default. We are still working on this but the driver manufacturers are working with us as we are calling functions that should work, but the drivers are crashing. This is bleeding edge development with NVIDIA and other hardware manufacturers working directly with us on a daily basis. 

Hardware acceleration is a new feature in 1.9.0 and if it does not work for you then turning Hardware acceleration off is not "degrading the software" , it is making it use the same codepath that 1.8.5 used to draw, so is as fast as it used to be.

[george++]

I am sure that the Affinity team is working on this (and other) issues.

Although I am not a professional graphic artist, I have used in the past many similar applications. So far, this suite is one of the best I've used.

[Linslusen]

Hi Affinity, I guess I'm currently holding an unofficial world record of crashes during one session (last night). I was trying to create a stack from 22 sky RAW shots, in order to create a star trail image. The stacking took some time, but eventually appeared, but when trying to edit the stack following James Ritson's video it crashed. I started anew, new crash, succeded in saving the file, but never got around to Flatten the stack, the program just froze or crashed. Not possible to export the file to a JPEG. Not possible to export a slice. I've tried the same procedure in the Beta with similar results. It seems that after the last update or two updates, the program appears much more unstable, crashes at all occations (no pattern identifiable), and is visibly slower in loading RAW images. This is really no fun at all.

[Komatös]

@Linslusen Hello, please provide us with information discribed here:

https://forum.affinity.serif.com/index.php?/forum/71-bug-reporting/

[Gabe]

@Linslusen Please create a new thread by following Komatös' link. Your issue is completely unrelated to the original issue reported here...

[Linslusen]

6 hours ago, Gabe said:

@Linslusen Please create a new thread by following Komatös' link. Your issue is completely unrelated to the original issue reported here...

Sorry about that. I'll do that.