Constant Crash after 1 to 5 minutes Windows 11: Insane!

[Remi Turcotte]

Rare crashes (if any for weeks, seriously) on last most recent affinity photo v1.x for quite a few years on my old trusted Windows 7 pro, with 2 xeons, and 16 gigs of RAM...

Now I get this Brand new Windows 11 OS, 128GB Ram, I9 CPU, Plenty of SSD, and a 3080Ti.

6000$ friggin box PC, shoouldnt I be able to edit... 2D pixels?

What convinced me to upgrade to V2 was that since I moved to Windows 11 with the lasy V1, that last most recent V1.x started crashing a little more...

Now I've upgraded to V2.0.0

Crash after a min.

Restart. Crash after 3 minutes.

In performance, disabling hardware acceleration, or enabling it, using ANY retina Rendering mode, ANY renderer, ANY view quality, low or high RAm usage limit Disk usage warning updated graphic card drivers blaaaaah blah blah:

Random VERY frequent crash & quit.

Affinity photo has not lasted even half an hour this entire week.

Nothing else, and I mean NOTHING has crashed on this PC since I got it, and I do web, video edition, 3D in realtime and renders!!!

I crash every 1 to 5 minutes or so, how can I work like this ?? This is insane!

I'm going to reinstall my last newest V1, and wait for the next V2 update before event starting V2 again.

One last thing:

I read a few people complaining about the price,

I've got the full cross platform licence, and I think its a VERY great price, but jesus, so many crashes...

 

[Chris B]

Hey Remi Turcotte,

With your new system, I would not change any of the Performance settings in Preferences. We have as imilar setup (same CPU, GPU etc.) and I do not have any crashes. It sounds like you are actually triggering a crash by a certain action or with a certain tool. 

Can you go to %USERPROFILE%\.affinity\Photo\2.0\CrashReports\reports and see if there are any recent crash reports that you can attach?

A bit of info about your workflow would be helpful too. What tools do you commonly use, do you work with raw or bitmap, are you in 8, 16 or 32 bit etc., are you copy/pasting, do you work from a cloud/external drive etc.

 

[Remi Turcotte]

12 hours ago, Chris B said:

Hey Remi Turcotte,

With your new system, I would not change any of the Performance settings in Preferences. We have as imilar setup (same CPU, GPU etc.) and I do not have any crashes. It sounds like you are actually triggering a crash by a certain action or with a certain tool. 

Can you go to %USERPROFILE%\.affinity\Photo\2.0\CrashReports\reports and see if there are any recent crash reports that you can attach?

A bit of info about your workflow would be helpful too. What tools do you commonly use, do you work with raw or bitmap, are you in 8, 16 or 32 bit etc., are you copy/pasting, do you work from a cloud/external drive etc.

 

Hey there, I posted this to signal there are issues with V2

I appreciate you trying to help supporting me and my little V2 issues.

Seriously, thank you.

That said, yes, I agree, I surely trigger crashes by doin certain actions and using certain tools: thats what I bought photo V2 for.

I know that usually nowadays the mainstream misconception is that you gotta start working for free, for hours, as a debug quality control employee, providing reports and describing the exact condition into which the product failed and crashed, so that the coders who created the product may correct the situation without spending a dime into quality testing the said code but yah, nope.

Truth is I dont give a F that much, after posting my initial rant, I spent the rest of my evening on my reinstalled V1.10.xx and had NO problems whatsoever, which is the extent of effort ill give to thoses issues.

My contribution stops at signaling there are issues with V2 in that ungracious way, "that" helped me getting rid of the frustration of paying for a broken beta version.

And that was "free" at no charge, my pleasure (hahaha)

I doubt they do, but if someone at Serif reads this, at least they can act now and fix the bugs.

Best of luck if you use V2 and you dont have any V1 licence

[Remi Turcotte]

An update  for whoever read this aside the affinity team e.g. buyers, beware:

It's 2024,

two years later, as I tried from time to time to see if this bad joke would run any better:

Many MANY versions later, my affinity photo v2  is now at v2.5.3

It still just quits and crashes randomly in minutes of being opened...

Totally useless.

Can't rely on this AT ALL to work.

Doesnt even generates error reports in the folder, all the while ALL my other softwares (and as a veteran 2D/3D artist I use a SH1TLOAD of various ones) runs flawlessly, (including my affinity photo V1, which is what i still use) since I upgraded to windows 11 pro...

...

Draw your own conclusion, I for sure wont ever buy anything from Affinity again.

This is my last post, I wont come back here to update.

 

[Chris B]

Above, I asked for a little info regarding workflow to see if we can figure out the trigger. You did not provide any clues about tools, document types or personas so we had nothing to go on. 

If the crash is occurring within minutes of the app being open, a short screen recording may also offer some ideas as to what is happening. Perhaps a certain tool being used in a certain way is causing this.

It's unfortunate that you said you will not be returning to the forum but I'm here to help if you want it - I just need some more information so that we can begin diagnosing what's going wrong. 

[LGJ]

I would like to revive this thread. I have an ASUS Proart Studiobook Windows 11 i7 Nvidia 3070TI with 32GB or ram. ALL of my drivers are up to date (Windows GPU and NVIDIA GPU). I get nothing but crashing with v2. The problem plagued me when I first bought this machine a year ago, after months of crashing an update from Affinity "fixed" the issue and here I am on 2.5.3 and back to the constant crashing. The real problem is the crashing completely looks up my machine and I have to hold the power button down to kill it. Any unsaved work I have up until that point is scrapped. Seems as soon as I pan an image, CRASH! In painting brush tool, CRASH!!, zoom, CRASH!!! Maybe crash is not the word and this should be more like critical failure causing my entire machine to lockup. This is not an isolated thing and there are other threads on here and on reddit with people having the same exact issue. What do I need to provide Affinity to figure this out and make the problem go away? If I bounce back to Affinity v1, zero issues. Zero. Everything is smooth as silk. There is some garbage code in v2 causing this problem. 

[LGJ]

Also, no recent crash report to upload since this program completely hoses up my machine. 

[walt.farrell]

11 minutes ago, LGJ said:

If I bounce back to Affinity v1, zero issues. Zero. Everything is smooth as silk. There is some garbage code in v2 causing this problem. 

You could try reverting to 2.4.2 and see if that fixes the problem. You would need to uninstall 2.5.3, download 2.4.2, and install it. 

Or (though it might prove a bit confusing) you could install 2.4.2 using the other installer. That is, if you've installed 2.5.3 using the MSI/EXE installer, you could leave it installed and install 2.4.2 using the MSIX installer. They will coexist, though:

• You will need to make sure you don't try to run any of the Affinity V2 apps using MSIX while any are running using MSI/EXE (or vice versa). In other words, run only 2.5.3 or only 2.4.2, don't try to have both running at the same time.
• The Windows Start menu will be confusing as it will show two entries for each of the applications, and it's hard to distinguish them.

Note that you could try this with just one of the apps, such as Photo or Designer, that you regularly have problems with, rather than doing it with all 3.

14 minutes ago, LGJ said:

Also, no recent crash report to upload since this program completely hoses up my machine. 

You could check the Windows Event View logs; they should have information even if you don't get crash reports.

Also, have you tried disabling Hardware Acceleration (OpenCL) in the application Settings, Performance? It can often help. It will require an application restart to be effective.

[LGJ]

1 hour ago, walt.farrell said:

You could try reverting to 2.4.2 and see if that fixes the problem. You would need to uninstall 2.5.3, download 2.4.2, and install it. 

Or (though it might prove a bit confusing) you could install 2.4.2 using the other installer. That is, if you've installed 2.5.3 using the MSI/EXE installer, you could leave it installed and install 2.4.2 using the MSIX installer. They will coexist, though:

• You will need to make sure you don't try to run any of the Affinity V2 apps using MSIX while any are running using MSI/EXE (or vice versa). In other words, run only 2.5.3 or only 2.4.2, don't try to have both running at the same time.
• The Windows Start menu will be confusing as it will show two entries for each of the applications, and it's hard to distinguish them.

Note that you could try this with just one of the apps, such as Photo or Designer, that you regularly have problems with, rather than doing it with all 3.

You could check the Windows Event View logs; they should have information even if you don't get crash reports.

Also, have you tried disabling Hardware Acceleration (OpenCL) in the application Settings, Performance? It can often help. It will require an application restart to be effective.

Going back to 2.4.2 seems to have stopped the freezing? I appreciate the suggestion! What is up with the new versions that's causing the crashes?

[walt.farrell]

38 minutes ago, LGJ said:

What is up with the new versions that's causing the crashes?

What does the Event Viewer show about the freezing?

[LGJ]

31 minutes ago, walt.farrell said:

What does the Event Viewer show about the freezing?

So tricky question to answer as there is a lot of info in the Event Viewer. I had 3 freezes today and 2 or three yesterday. Around the time of each freeze the following event was logged: 

The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\WINDOWS\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.

I'm unable to find a specific event where a crash was reported on the above event seems to be linked to all the crashes. 

[walt.farrell]

I'm not sure what those messages mean.

All I can suggest is following the instructions in the FAQ (and the Microsoft site it points to) and saving the application and system logs, and uploading them.