Affinity Photo Memory Crashing

[Puddy Tat]

I updated to the latest version 1.7 and I've had so many memory problems since. When I attempt to rasterise, refine a selection, use the gradiant tool affinity slows down windows to the point its unresponsive and the only way to resolve is to switch off my computer. 

On restart all is well until I again do one of the above and 90% ram is used up even when I use the gradiant tool on its own.. My dell computer is more tham compatible for affinity having 8g ram.

I opened a small 1mb jpg and attempted to use the gradiant tool, immediately affinity became unresponsive. On checking the windows task master processes affinity Photo was using 5gb of ram out of 8gb. This surely isnt correct for a 1mb file using the gradiant tool. 

I've tried the following :

Adjusting windows allocated memory

Adjusted for best performance. 

Fresh install of Windows 10 then installing affinity photo 1.7.Only affinity photo installed. 

Adjusted performance settings within Affinity Photo according to forum recommendations. 

Installed on another Windows 10 computer with higher spec than mine. 

All of the above made no performance enhancements, affinity still used up 90% of ram in all configurations and Windows froze up. 

I have installed the previous version of affinity 1.65 and it works perfectly. There is obviously a bug within version 1.7.

Please resolve asap. 

Thank you

Chris. 

[Ron P.]

Welcome to the forums @Puddy Tat,

This is not normal. The staff are going to ask for more information and possibly the file you're seeing this high ram usage. So could you post your system specs and attach the afphoto file?

I know you mentioned Photo being the only app installed and you're seeing up 90% Ram being used. I'm also using Win 10 Home, latest version 109. While I have considerably more Ram, 32 GB, Photo does not consume anymore than 3% of my Ram. While testing your issue I had this browser window open, while running a bunch of background services, to include my antivirus. Still my total ram usage was only 12%. The test files I used were around 24MB, and I applied gradients, and much more demanding Live Filters, still it did not cause Photo to use most of my Ram.

 

[Puddy Tat]

Hi Ron

I have an update, a positive one, thank goodness. I decided to grab some screen shots of windows task manager while running affinity 1.6.5 using the gradient tool. It showed affinity using 230mb, as i would expect. I then shut affinity down and downloaded the newest version 1.7.1.404. I then shut down my pc to make sure all memory was cleared so nothing was lurking in the corners, and restarted. Once loaded I updated affinity to the newest version and launched it once installed. I opened the exact same file (only 2mb by the way), added a new pixel layer, grabbed the gradient tool and created a gradient. Its at this point task manager would be showing 5gb memory out of 8gb being used by affinity. However, I was more than pleasantly surprised, (in fact, I was ecstatic i can tell you) to see in task manager that only 258mb was being used by affinity. Hey Presto, problem resolved and I'm now cooking with gas and not banging my head on the wall (not recommended).

I'm not one to normally tempt fate, however, on this occasion I thought i'd give it a go. I opened a few files totalling 60mb, and the memory used only went up another 100mb. Hey Presto, I'm a happy bunny.

I have attached a screen shot of task manager showing affinity 1.7.1.404 using  only 258mb.

My conclusion (though it may not be true?), a possible glitch within Windows  when I first updated to the newest version of affinity, thus causing a major memory outage. I see that others on the forums are experiencing the same memory problem as I had. If you come across any of them please do direct them to my post to enlighten them how to resolve the problem.

Many thanks for your reply Ron, catch up soon yeah.

Chris, Surrey, United Kingdom.

[Ron P.]

Glad you got it working right.

[Mark Ingram]

@Puddy Tat, I'm glad your problem seems to be solved, but I will just say that looking at Task Manager and the memory usage in between document loads isn't a reliable indicator of memory issues with our apps. If you start the application, look at the memory usage, then load a document, zoom in and pan around, then close the document, you might expect the memory usage to drop back to where it was when the application first loaded - but this isn't the case (and is the expected behaviour, since 1.7).

[Puddy Tat]

Hi Mark

Thanks for your message. I'm not having the experience that you mention above. I loaded a document as you suggested, zoomed in, panned around then took note of the memory being used according to the task manager , memory being used was 439mb (see screen shot memory1). I then shut down affinity photo and you can see from the next screen shot (memory2) that task master showed no memory being used by Affinity. I then opened the same file, made a selection, began to refine the selection and you will see from the screen shot  (memory3) that affinity was using 3384gb of memory. Surely Affinity shouldn't be using 3384gb of memory when refining a 12mb document, thats a ridiculous amount of memory.  You can see from the screen shot that all the other programs running underneath Affinity are windows operating processes as per normal. This leads me to the conclusion that Affinity has a hidden glitch. I've noticed there are a few reports on Affinity forums regarding huge memory problems such as I'm experiencing too. We cant all be wrong, or can we? When I revert back to version 1.6.5  using the same document, same windows, same computer, I never experience huge memory usage with Affinity.

Your help in this matter would be extremely grateful

Thank you

[Mark Ingram]

1 hour ago, Puddy Tat said:

Surely Affinity shouldn't be using 3384gb of memory when refining a 12mb document, thats a ridiculous amount of memory.

I assume you mean 3384MB, from your screenshot (3384GB would be pretty ridiculous).

3384MB amount of memory usage is pretty small to be honest, and using memory (or CPU) isn't a problem - the aim is to utilise as much of your computer as possible (i.e. if you bought a machine with 64GB of RAM, you wouldn't be happy if we only used 2GB of RAM during normal operations). If you aren't happy with the amount of RAM the app uses, you can limit it in Preferences, but note that this can have a negative impact on performance.

[MauricioC]

I'm having the same issue immediately after upgrading to the latest verision of AP. 7310MB for  a file that is 122MB when saved. My computer crashed several times and is struggling to keep up with the simplest tasks like sampling a single color with the eyedropper, or taking one step back in history.

[tyrantrent]

I'm having the same issue however ap is using over 12000mb just after  I develope a photo. I rasterized or attempted to and ap becomes unresponsive and I have to force quit.1.9.