Extremely Poor Performance on One Specific Document?

[Mr. Mendelli]

I'm working on a document in Affinity Photo v2.5.7 that I have noticed considerable performance issues with and nothing I have looked into makes sense:

- I have hardware acceleration enabled
- RAM use is set to 8GB (of 32GB)
- I have rebooted my PC multiple times
- I have checked for pending updates
- I have cleared caches
- I am not low on disk space
- Other programs are running normally
- I have tested other documents already

This one is very puzzling for a number of reasons, aside from what I have listed above, my document is extremely optimized and lightweight. The canvas is only 1024x1024px, all elements are shape layers with only one layer effect, and the whole document is roughly half a megabyte. In terms of performance issues, it is excessively slow to open, edit, and save. Anything I do takes magnitudes longer than even much more complex documents. Attached is the document in question in it's currently afflicted state.

Specs:
OS: Windows 10 x64
CPU: AMD Ryzen 5 7600X (@4.7GHz)
GPU: MSI Ventus 3X OC GeForce RTX 4070 Ti Super 16GB (DDR5@6400MHz)
RAM: G.Skill Trident Z5 RGB 2x16GB (DDR5@6400MHz)

tex1_64x64_m_fefe12c9bdfa636e_5.afphoto

[GarryP]

It took my machine around 25 seconds just to load that document.

My machine (Windows 10) isn’t quick by any modern standards but from what I can see in the document it shouldn’t have taken anything like that long.

Using Save As to create a copy also took way longer than I thought it should, around 15 seconds.

However, removing the hidden Group (the one with the Gaussian Blur Live Filter) seems to have made the timing problems go away so that’s maybe somewhere to start looking (making that Group visible produces an effect I wasn’t expecting).

[carl123]

The Live Gaussian Blur filter is "corrupt", even if not visible it affects the document's performance.

You can safely delete it and recreate it with the same values - if you actually need it

[Mr. Mendelli]

Thank you, I've never encountered something like this in the years I've used Affinity software before.

Update:

This may actually be a bug, I observed identical behavior with a different source document and have submitted a bug report after being able to replicate the behavior.

[Lee D]

@Mr. MendelliI've logged your file from this thread with our developers to take a look at. 

I also took a look at the one in your bug report, like @carl123 I'm not getting any performance issues with the file. However as it also shows the same type of issue with the Live Gaussian Blur I've added it to the report as well.