Jump to content
THESE FORUMS ARE READ-ONLY: Please Read Me ×

Recommended Posts

Posted (edited)

Can't open any exiting file or create any new file using 1.7.2 on MacOS 10.14.5. Just get the beachball forever. Using very little CPU and zero disk or network resources. Process samples show that the application hangs about once per second.

Attached process sample.

Sample of Affinity Photo.txt

Edited by MacDavePro
  • Staff
Posted

Hi MacDavePro, welcome to the Affinity Forums.

Could you please go to \Users\username\Library\Containers\ and rename the folder com.seriflabs.affinityphoto to com.seriflabs.affinityphoto.old

This will perform a reset on the app whilst backing up any user settings (and can be restored if needed). If that works., could you attach the folder you renamed here so we can try and replicate the environment?

I assume this is a recent issue with 1.7.2 or have you just updated?

Posted (edited)

Hi Chris.

Thank you for the very fast response.

Later in the day I noticed odd behaviour in other GPU accelerated apps. I have a number of them concurrently open throughout the workday and haven't yet isolated the culprit but it seems from a spindump that some system resources were locked that Affinity needs in order to open a file. When the Apple Photos app exhibited similar behaviour it was pretty clear I had a systemic problem. Some candidate bad neighbours are Zoom,  Skype, Chrome and Safari Preview.

Short version - after a reboot Affinity is back to working as expected. I was probably a little quick on the trigger filing a bug report before even a reboot, but having been a *nix user for almost 30 years I'm just not used to rebooting very often ;) 

----

Can't see any way to close this bug - but then I guess we are using forum software for bug tracking. Feel free to delete the thread to reduce noise.

 

Edited by MacDavePro
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.