DigitalVisuals

Affinity Photo has always been unstable - but more so in the last week - to the extent I cannot use it professionally anymore.
I crashes randomly - often after 10 mins of work - but different times - different activities. If I repeat the steps it will not crash the second time.  Sometimes it crashes when I'm not even using the program (when working in another program like Chrome or Notepad++).
Using version 1.10.4.1198. Windows 10. ASUS ROG laptop GL503VD with Nvidia GeForce GTX1050 (using) and Intel HD graphics 630. Using two screens - one 2K. 
My computer is very stable. I keep it updated. I don't have problems with any other software - adobe, DaVinci, CuBase, etc.
No real support centre? We have to post here publicly?  Wow. I have work to do, so I can't be spending hours on forums trying to get a "professional" program running. This shouldn't be happening.
I don't see hardware acceleration under Peformance.
I've checked out 
 
 

Fallen
A return to inking....and a bit of experimentation 
AD 1.8
Original size 1500 x 500mm 300dpi
Uploaded at 3543 x 1181 jpg

Fallen:Sepia Version

 
Fallen:Coloured Version

Foreground Tree Structural Build and Wireframe

Tulip Plant Wireframe

I have already tried previously to disable Open Cl. Will try again with more memory.

@Chris B  have not seen that. But thanks
 

@Studio97Visuals I've hidden that last reply of yours because it contains a visible email address. If you're happy, I can unhide it but it is visible to mods in it's hidden state.

I have just installed Windows 11 and have found that when using Affinity Photo the menu text behaves in a strange manner, after loading an image some of the menu items disappear and it is necessary to hover the mouse curser over them to make them reappear.
Also some of the tools graphics become corrupted when changing values.
No other programs or software which is installed on my PC behaves in this way.
See attached photo

I know it's different but I don't think it's necessarily less intuitive than using save-as.
As far as I see it save as was not always there for "saving as a different format", it was there to save ayour current project AS a different PROJECT - useful for making various options or using previous work as a base to do something new. I actually think it was pretty lazy of certain programs to bundle in the exporting of that file to different formats in to the save as function. And, whilst this may be common to some programs, it certainly isn't to all. 
I don't quite understand why you say it is an old-fashioned UI/UX, imo it's actually a more considered choice, with using save-as being an antiquated "choice".

I personally don't find it at a struggle to scroll the extra few lines down from "save as" to "export" in the menu (I certainly don't find it harder to find at all) when I want to export, nor do I find it a hassle to remember to press alt as well as ctr,, shift & s as a shortcut to export my creation to a different file format. I'm not really sure what it is you are asking Serif to "spare us" from.
I actually don't save my work as jpg most of the time. If I'm using affinity to create a file I want it preserved in that format in case I want to make changes to it, or use it to do something new. I do of course want to export it as jpg (or png, etc etc) at various points, but this is a separate exercise to saving my work.
In my opinion it is good that the two separate functions of saving a layer based affinity file, and creating a flattened file format is separated as they are. Export is a perfectly logical choice for creating a jpeg as that is exactly what you are doing - exporting your file to something which is fundamentally different to what it is. I welcome this kind of clarity of function.

I'm not really sure I see why there is any difference from a work flow perspective between choosing  "save as" or choosing "export" when you want to export a jpg from your file anyway... the only thing I can see is force of habit and one additional key modifier - neither of which seem a good enough justification to  present it as a big issue or poor design decision.
I honestly feel like this request boils down to "I'm not used to it being called export instead save-as"... and the perception that this is a wrong choice or somehow creates a stumblingblock to creating jpgs, pngs, etc, flows from that. Choosing export rather than save-as in the (same) menu, or pressing alt as well as shift s is not "inherently any more difficult as an operation, it's only really user habit that may make it so - which really needs to be considered against the reasons why it was done differently, and the fact that it won't actually be the case for eeryone, only a certain group of people. Personally, even having extensively used photoshop, I didn't really have any issue getting accustomed to this difference. This could be because other programs I also use a lot do it already though.
I personally hope Serif don't make this change as I prefer it as it is.
Just my opinion but I thought it worth adding the counter-point to your request.

I working with the Beta on a windows 11 setting on 75hz with 32 GB ram and a Nvidia GPU.  Where the 1.10.1 has several problems, the beta is working how it should.

I working with the Beta on a windows 11 setting on 75hz with 32 GB ram and a Nvidia GPU.  Where the 1.10.1 has several problems, the beta is working how it should.

I working with the Beta on a windows 11 setting on 75hz with 32 GB ram and a Nvidia GPU.  Where the 1.10.1 has several problems, the beta is working how it should.

I working with the Beta on a windows 11 setting on 75hz with 32 GB ram and a Nvidia GPU.  Where the 1.10.1 has several problems, the beta is working how it should.

I have testet today witch the beta 1.10.2 on 60 hz, and have no found problems.  If I do this with 1.10.1.xxxx then it freeze up.
So I stay for now and use the beta 1.10.2.xxxx 

I was going to ask if you have Nvidia G-Sync interfering somewhere. You should be able to run at 59/60 hz which is standard for a HD monitor.

I have tryed today the beta and I have to say, its working without freezing to now under Windows 11 home.

I will stay up this one, hope to get a crash report to, Thanks so far Chris

I'd be surprised if the refresh rate was anything to do with it, unless G-Sync was doing something funky. 
I've just ran the dmp file you uploaded again but I think my newly upgraded Windows 11 OS is playing up so I need someone to check it on their machine. I'll get back once I've had it checked. It may be worth attaching another dump from Task Manager when the apps is frozen so we can cross reference. 

My work laptop updated to Windows 11 this morning and for the last hour I've been painting and masking with no issues. Can you give me a bit more info on the type of document you're working on? Such as dpi, resolution, colour mode etc?

It could be Windows 11 like you say. We have only seen Windows 11 on the Windows Insider Program via a VM - we do not have an ISO yet.
You definitely seem to be having some serious issues on a machine that is still very capable... 

It's not always relevant to compare how one app runs to another. If Windows 11 isn't functioning with a driver or something else Affinity requires but your other apps do not use/require them then they of course will not crash.
I'm going to try and install a Windows 11 build on a local machine and work for a day in it and see what happens. I would prefer not to run it on the VM that we have.

Hi @Studio97Visuals,
You would need to "Create DMP file" from the Affinity Photo.exe process, not the crashpad handler. Or see if you can have any in here. Only attach the most recent 1-2
 

The round corners will be the new standard I think.

Same here. I use Windows 11 since the first beta release and Affinity Photo for my daily work. All without issues. I have OpenCL ON. Since the last release of Affinity Photo it runs well here (before it was slower, also on Win 10).
My setting is similar to yours  Intel I5 10400, Nvidia 1050 ti
(round window corners  to match the windows 11 style would be nice)

Why waste resources for features available for free or very cheap and affordable  elsewhere.   I would rather want them focusing on making the soft a  flexible modern non-destructive image manipulation soft  where you could construct such things on your own  from  a stack of a few basic displace, posterize, flood fill  and edge detect live effects  and tweak every aspect if it on the fly.