Jump to content
finedesign

Trying not to hate you, Affinity Designer

Recommended Posts

I just spent over an hour on a design. AD crashed as I was saving and the recovery file had NONE of my edits! It only shows the original file.

 

The original file was a jpeg, and I was using it as a guide to draw something. On save, I tried to navigate to a part of my file structure, and the app crashed. And this was not a complex design.

 

So furious.

Share this post


Link to post
Share on other sites

Please forgive this somewhat off-topic post, but regarding Affinity getting crash reports, I have enabled both "Send diagnostic & usage data to Apple" and "Share crash data with app developers" in my System Preferences > Security & Privacy > Diagnostics & Usage.

 

Very occasionally AD or AP has crashed so I wonder if Apple is sending my (or any other user's) crash reports to Affinity.


Affinity Photo 1.7.2, Affinity Designer 1.7.2, Affinity Publisher 1.7.2; macOS High Sierra 10.13.6 iMac (27-inch, Late 2012); 2.9GHz i5 CPU; NVIDIA GeForce GTX 660M; 8GB RAM
Affinity Photo 1.7.2.153 & Affinity Designer 1.7.2.6 for iPad; 6th Generation iPad 32 GB; Apple Pencil; iOS 12.3.1

Share this post


Link to post
Share on other sites

I had this issue.

It's very tempting to choose 'Save file with history' and I did so. After couple of days of working with the same file, the history apparently became overloaded. The file was slow to open and AD crashed frequently As soon as I disabled 'Save with history', saved the file, closed and opened it again, the problem stopped. Everything works smoothly.

Share this post


Link to post
Share on other sites

This looks like a (known) bug in OSX.  I think we've seen this before with the Save Panel causing crashes.

 

Someone will take a look at it and see if there is anything we can do.  We will also report it to Apple.


SerifLabs team - Affinity Developer
  • Software engineer  -  Photographer  -  Guitarist  -  Philosopher
  • iMac 27" Retina 5K (Late 2015), 4.0GHz i7, AMD Radeon R9 M395
  • MacBook (Early 2015), 1.3GHz Core M, Intel HD 5300
  • iPad Pro 10.5", 256GB

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×