Jon P

Hey @MikeTO, That document is mostly missing linked remote images as you expected, the one image provided is loading as OK and not modified for me, and there's no other images to re-link that were uploaded. The document that you load in to the beta that reports everything as modified, if you save as a package I assume it then doesn't load back as modified so that can't be sent? It may be useful as atleast I can then modify all the resources to force the longer load and reproduce what you are seeing. I've done a quick test linking 100's of images, and then modifying them and the load time seemed similar, but it may be a bit more complicated than the simple test I created (just multiple 10mb JPGs). If I can reproduce this longer load I was going to log that to see if we could do better, but the real issue is what's causing the app to think they are modified in the first place. I assume that's not something you've been able to reproduce in isolation, and only the one specific file with linked images is thinking they are all outdated? It could very well be that it was loaded and saved when this bug was present that's now fixed?

@Krzysztof Petrus Can you make a post in the bugs forum if you can reproduce that in the current retail build. I've just placed a PDF, modified it externally and updated it and there was no crash, so a video/some example files will help us reproduce the issue you are experiencing

Thanks @Hangman that's been logged with us through that thread. I've logged an improvement about also adding it to the Layers dropdown, which would allow it to be assigned a shortcut

Thanks @MikeTO, It may be by design since the frames are linked and it's jumping you to the end of the frame it's just updated, but I've logged it

Hi @MikeTO, I've logged 2,3 & 4. Am struggling to see what you mean by 5 if you don't mind posting a video to demonstrate, and will poke around 6 and see if I can reproduce anything, for now it seems to be undo'ing correctly

Hi @Gustavo Reginato, The issue created for this is still open and has not been marked as being in 2.2. If it gets added it will first appear in a beta, but it's correct that it's not currently in 2.2 since the report is still open. I'll bump the issue, but we can't say for certain if/when it will be added.

This guide should cover it, it shows all errors that may happen, and am curious if when it hangs there are errors relating to affinity in that log, it may help us troubleshoot why you are seeing the hang

Hi @jubarbie, If you see this again, can you open the console and filter any errors by Affinity and let know if there's any errors that appear there?

Hi anto, I can't see too much from the crash report. Is this crash reproducible and what were you doing at the time of the crash?

This has been already raised internally Mike, and is currently by design. The key thing here being that you were on spread 282-283, and then scrolled to 212,213. So when you switch to that spread and click on it so it is active, then click "Previously viewed page", it is taking you to the previous view you had, which includes the scrolling that you did when on that spread. If you open on 282, then use the pages panel and jump to another page, it should then switch you between the spreads. I'll add your observations to the issue we raised internally. Out of curiosity, in this scenario, would you expect it to ignore the scrolling you did, and display spread 282 regardless of where your view was before hand?

Are you able to upload the document here Mike? I'll take a look. You can upload the linked resources with it too and I'll re-link, or save as a package.

Could you let me know the full path of the folder that it's in when it hangs saving, maybe if I reproduce the folder structure I'll be able to see the hang when saving. I assume if you Save As to a new location it's also fine? I'm aware it's not an ideal solution, but until we can reproduce the hang you get whilst saving it will be hard to fix or pin point the cause, so will require some troubleshooting. For now moving the file seems to atleast work around the issue.

Hi @jubarbie, Are you opening and working with these files from your desktop folder? As that helped last time If you want to send me over one of the files that's crashing on save I can try reproduce it

I've just loaded that and re saved it, i'm curious if the saved file is still causing you issues if you load and save this file? I can get your crash dump looked into, but nothing is jumping out as obvious to me. To clarify, it doesn't matter where you are saving? You are saving onto a local drive (Desktop, Documents, etc?) and it's the same each time? LACE_613A-JP.afdesign

If you open the same file(s) in 2.0.4 are you able to save them or do you get the same hang?

This thread should advise you how to send over the crash file, which you can attach here. If you create a new document do you have any issues saving that? Or is it only certain documents you are loading? Thanks

Hi, I've tried a few machines here (Intel based and running Ventura) and it's saving fine. Are you able to attach the crash report? Thanks

Thanks, I've reproduced that and logged it

Are you able to attach the dummy file you were using?

I've noticed this before @walt.farrell. I've not been able to suss out what causes it, besides a bit of guesswork that some times we crash and it's not caught by the handler, and the crashpad handler process ends up not closing, and a new one is created on next run up.

@Adam13 If you can still reproduce a hang exporting slices in the latest beta, can you please make a post in the beta forums with some steps and potentially a video demonstrating the issue so we can reproduce it. Thanks

Thanks for the update, had a chat with Matt about it yesterday and he advised he was helping you troubleshoot it, so glad you got to the bottom of it. I'll see if I can reproduce the issue and then we can hopefully log/fix it to prevent it happening again.

I assume you followed similar instructions here, so are one step ahead of me, although I was hoping there'd be something a bit more useful in the output If you ran the command and output it to a text file "sudo fs_usage pid <PID> > output.txt" even if it just looped a lot, do you mind attaching the output? If you can send the log from AD that could be useful too. Good investigation so far though, it could maybe be permission related but i'd expect some errors, not for it to be stuck looping doing something in the background

Interesting that it's Photo only, and the slowdown seems to be coming from, and that a reinstall didn't help. Can you navigate to ~/Library/Application Support and rename the Affinity Photo 2 Beta folder Can you then navigate to ~/Library/Preferences and rename the com.seriflabs.affinityphoto2.beta.plist If you do both of those it will reset your settings (you can rename back to restore them), and I'm curious if that helps. If it does, sending both that folder and the plist over will be helpful, if not then it may be possible to track what cfprefsd is actually doing to cause the high cpu usage

Thanks for the report, I've logged this