Publisher freezes on exit

[Bryce]

I have Publisher 1.7.3 running on MacOS 10.15.2 (doesn't seem to matter) on a 16" Macbook Pro.

Problem: After having a file open that has a lot of links to large files - that I can edit just fine. I save and close and the Publisher freezes.

If I open the file and don't do any editing and just check resources, I can close everything just fine without it freezing.

While using it Publisher will be taking up 15-20GB of RAM and that is fine as there is 64 GB of RAM.

I have tried different things such as upgrading the OS but none seems to help. The Publisher file involved is actually small at 16 MB. I can post the file but the links are absolutely massive if need to attach that too at 10GB+.

It just feels like a resource issue and I'm not sure how to help.

 

[Patrick Connor]

Sorry.

Thank you for reporting a problem using 1.7.x . It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script.

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the current 1.8.3 release build.