Jump to content
You must now use your email address to sign in [click for more info] ×

Crash on document save


Recommended Posts

Alright, 1.8.1 is in my case a complete clusterflock of bugs and weirdness but this one definitely takes the cake. Costed me HOURS of work and happened twice in the past 2 days.

Scenario:

1. Work on a file for while (hour or two). All good during production, no issues or hangups.

2. Remember you haven't saved in a while.

3. Press Cmd + S

4. Look at your desktop wallpaper for a while wondering wtf just happened.

I have no clue whatsoever on what exactly caused the crash but I know something like this never happened in the last 3 years I've used Affinity products. If I can help in any way with this bug let me know.

In the meantime I'll try to make a habit of destroying the save button regularly. The worst thing is it's right after I save the damn thing and there's no recovery option afterwards of any kind. All progress is just lost.

Link to comment
Share on other sites

Is it the same file when it happens?

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites

4 minutes ago, carl123 said:

Is it the same file when it happens?

There have been 3 crashes now. The last 2 were in the same file. I'm not sure about the first crash but I think I was working on something else. You think the file is corrupted or something like that?

It might be worth to note that every time it crashed on document save it happened right after I did some artboard duplicating with a whole bunch of complex layers. Basically right after i beefed up the file size considerably. Maybe it's something to do with that.

Link to comment
Share on other sites

If you can reliably find a way to replicate the "crash" you can send the document to the support staff who will be then better placed to see what could be causing it and to provide a solution.

Alternatively, you can try using the latest beta to see if that is more stable for you. 

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites

6 minutes ago, carl123 said:

If you can reliably find a way to replicate the "crash" you can send the document to the support staff who will be then better placed to see what could be causing it and to provide a solution.

Alternatively, you can try using the latest beta to see if that is more stable for you. 

No dice. I've already tried repllicating it but I have no idea what's the trigger. If I find something more concrete I'll make sure to upload it to the staff. I was more hoping that someone else was experiencing this.

I don't want to risk more bugs by using the beta. Disregarding this issue, 1.8.1 is fine. It's just that this bug is such a slap in the face since it happens on SAVE and doesn't leave behind any recovery file. 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.