Photo CPU hogging

[Dieselelkins]

Photo has been working sweet for weeks.

but this week not so much.

it’s been cpu hogging and not responding. Often requiring end task.

this has been in various work flows.

from trying to apply a live filter distort to just moving a tool. Several times the brush kept changing size.

I also tried to export to a jpg. And after an hour ( yes I went off for my dinner ) it created a very small file size jpg which would not open reporting corrupt.

for two days I’ve barely been able to do anything with it.

support has been good. 
however I’ve not heard from them today.

Through support advice, ive changed renderer. Switched it back, uninstalled and reinstalled got drivers. 
this morning it worked well for 10 minutes then back to its antics.

pits driving me insane. I didn’t manage to get anything done today.

 

pc running windows 10

my pc has a xenon processor x5687 3.6ghz - ex cad server 

Gpu is Radeon rx570 

ram is 40 gb Dell  server ram. 
 

many thanks for reading

 

 

 

 

[RichardMH]

Sounds like hardware acceleration problem. Have you tried with it off? Edit->Preferences->Performance

[Dieselelkins]

Hi. Thanks for replying.
 

Yes acceleration was on originallly. It was the first thing Support suggested to change and untick it to off.

then change the renderer from the gpu to warp ( I originally encountered the  problem trying to use the warp tool using phot through publisher . Since then I’ve been using the actual photo app itself not through publisher ) 

then told to reinstate the gpu. ( support asked for the log.txt and seemed convinced it was a driver issue 
then uninstall the gpu driver and reinstall 

 

maybe I should turn acceleration back on!? I’m not at the machine right now, but I don’t think it’s been re selected. 

Support have been good at replying. Unfortunately I’ve not heard from them today. Hence asking here. 

 

[ashf]

Try to switch back renderer to GPU (RX570)
Also try to enable the Hardware Acceleration.

What's the version of the GPU driver?
 

[Dieselelkins]

Hi

thanks for reply

i did switch the renderer back - photo attached

I uninstalled and reinstalled the gpu driver on Thursday and had switched the renderer on Wednesday as suggested by support. They said from the log file that they were convinced it was a gpu driver error, hence the advice to uninstall and reinstall.

but photo still hogged the cpu 

 

[Dieselelkins]

Gpu driver

amd Radeon 

 

[Dieselelkins]

Tried again on a new file.

just background apps running.

simple text on a wall displace 

clicked on map from layer below

cpu all the way to 100% 

but also  the memory usage has shot to 29gb

Still not responding 5 minutes later 

[Dieselelkins]

And now it’s even more bizarre

the original picture I was working on was some 650 mb

after messing about for 2 days trying to set a displacement map it is now showing in windows explorer as having an error and now being 10.4 GB! 

the attached photo show the file having been copied to the NAS as backup on the 25th (yesterday) at 653mb 

the right panel is the same file (the original) on my PC now showing as 10.4gb! 

[Dieselelkins]

And 50 gb has disappeared from my hard drive space

was showing 72gb free now 27gb free. 
 

 

[RichardMH]

Have you got capture one installed?

 

 

[Dieselelkins]

6 hours ago, RichardMH said:

Have you got capture one installed?

 

 

Hi Richard, thanks for your response.

Thats a very interesting link.  However, no, i do not have capture one.

 

 

[Dieselelkins]

I ditched the huge 10gb file and picked up an earlier backup. Losing some progress but there was obviously something wrong with that file.

I worked on that backup for an hour or so before stopping to be with the family. Saved and closed down Affinity, then the PC.

This morning, now the file i worked on yesterday afternoon, will not open. Photo closes eveytime i try to open it. 

I tried to open it via publisher instead. Publisher told me that the file is corrupt. (photo said nothing, just closed)

Why would the file be corrupt? Im at a loss. If i try with the backup file, not only have i lost yet more work, i cannot be sure it wont simply do the same again.

Moreover, is there any point in working on anything else? It may happen to that too!
Is there support theat reads the forum?  Ive emailed a few times sonce friday but heard nothing, which is suprising as they were very quick before.

Thanks

[Dieselelkins]

the crash report from this mornings event -

[User_783649]

@Dieselelkins In your screenshots I noticed that you're using file from your NAS and another one — from OneDrive folder. I've seen so many problems with apps (not just Affinity) when working with project files over network or from folders that might be in constant sync (Dropbox, OneDrive, etc.).

Just as a rule of thumb: never ever work with files from such locations. It is always better to copy file to a more safe place (local one, which is not modified by other apps) and then put it back once you've finished your work. Things can go really weird sometimes if you not following this more safe workflow.

[Dieselelkins]

20 minutes ago, Alex M said:

@Dieselelkins In your screenshots I noticed that you're using file from your NAS and another one — from OneDrive folder. I've seen so many problems with apps (not just Affinity) when working with project files over network or from folders that might be in constant sync (Dropbox, OneDrive, etc.).

Just as a rule of thumb: never ever work with files from such locations. It is always better to copy file to a more safe place (local one, which is not modified by other apps) and then put it back once you've finished your work. Things can go really weird sometimes if you not following this more safe workflow.

Interesting

Setup is actually that Affinity is on the C drive which is an ssd

Ive since read that affinity creates huge scratch / working files and people have suggested that their ssd fills up quick - which sounds familiar to me!

My files are on my machines on e drive being a mechanical drive.

they sit in the Onedrive folder on E drive, so onedrive auto backs up for me - do you think its auto synch back up might be causing problems?

 

The file on the NAS was me copying my working file to the NAS when it started becoming slow and stuttering.

Since then the file on E drive was the one that for no apparent reason went to 10GB (from some 600MB)
I ditched the 10GB file - had to as it also, for some reason, ate up some 50GB of my SSD and MS Windows kept telling me disk space was low.
So i copied the NAS backup file back onto my desktop to try it again.
It was that filed that I worked on yesterday afternoon  - after removing the 10GB file - and it seemed to be okay

I saved it to E drive

This morning it will not open and the above is the .dmp

[Dieselelkins]

Ive just tried it on a different machine and the same thing happened.

Tried to ooen my file, Photo simply closed down.

[RichardMH]

I don't think support works on weekends, which maybe why you haven't heard from them.

[Dieselelkins]

1 hour ago, RichardMH said:

I don't think support works on weekends, which maybe why you haven't heard from them.

A shame.

i did bring this up on Thursday and several times on Friday.

Fingers crossed tomorrow they can read this !
 

I unchecked open cl (again) and ive got Photo working. But the file is still corrupt. 

As before, ive opened an earlier version of the file. Before opening, I copied it to my desktop.

Ive down one thing to it. Drawn a circle, coloured it and applied a gradient. 

then saved it.

The file says it is 700mb

But my c drive has gone from 70gb free to 1.5 free.

There is nothing i have found in the spec for Affinity that suggests the program requires a hundred GB disk for its own use.

 

 

 

[Dieselelkins]

And 50 gb has disappeared from my hard drive space

was showing 72gb free now 27gb free. 
 

I’ll put this up and hope support can look at the thread tomorrow 

from the pics

the photo 1.0 temp file shows 47.3 gb 

click into that file and it’s on a .dat file

the rest of the 70gb is I. The roaming folder 

thanks