Jump to content

Recommended Posts

Posted

For the last two updates, I have been experiencing near constant crashing even when Affinity Publisher is just idling. There is no consistency beyond it occurring when I have an older V2 document open for copy and pasting. The document I'm working on is now over 100 pages (as is the original document). It doesn't appear to be a memory issue, the system isn't lagging prior to crashing.

Is anybody else experiencing this or is it worth me totally uninstalling and reinstalling? Will I lose my System Palettes if I do?

Apple M1 MacBook Pro, Ventura 13.6.4, Affinity up to date, 8GB ram

  • Staff
Posted

Hi @Natters,

Could you provide a copy of the crash reports, as well as a copy of the document(s) where you're typically experiencing these crashes? We can then look into this further by confirming if it can be replicated and the potential source of the crashes. I've provided a private upload link below if you don't wish to share the file publicly.

https://www.dropbox.com/request/WP8UKTDiWG02kW1P2xDo

Crash report FAQ:

Thanks

  • 2 weeks later...
Posted

Hi @NathanC

I've sent the crash reports but not heard anything and still battling with this. It appears to be an issue with the Affinity Store - which I don't even have open.

Termination reason: Namespace SIGNAL, Code 6 Abort trap: 6

Terminating Process: Affinity Publisher 2 Affinity St [2190]

Application Specific Information: abort() called

  • Staff
Posted

Thanks @Natters for sending them over, I should've included this on my previous reply but for future reference please reply back on the thread once you've uploaded the contents as we are not automatically notified when files are uploaded.

The process name in the reports is listed as 'Affinity Publisher 2 Affinity Store' which makes it easy to identify if it was originally installed via the Mac app store or directly via the Affinity store, the store is not the cause of the crash.

I've had your document open for a while and I'm able to freely edit your file without any subsequent crashes. However, I don't have access to any of the many linked resources used in the document. Based on this factor and the crash report backtrace indicating towards the app communicating with your dropbox link leading up to the crash I believe this may be the source of the problem.

Unfortunately I don't have a way of identifying any specific resource or location from the crash report as the cause, but what you could try is downloading the resources so they are stored locally instead of on dropbox, and then unlinking from dropbox in the app 'Linked Services'. Hopefully this should then cause the resources to become unlinked in resource manager, so you can then use the 'Relink' function from resource manager to re-associate the file paths of the local resources and then see if this prevents the intermittent crashes.

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.