unicon

Hey @Oufti wow, thanks for adding this behaviour to the list! Just tried CMD + A before copying, and indeed that loads even longer and completely brings the application to idle - even though the file includes only a single art board.

Hey Mike, Thanks for your answer, besides this issue, the pasteboard inspector is super interesting! What is it called? Also nice to learn that pasteboards copy multiple versions (for different purposes). Makes total sense! The similar timing of ~14 seconds on closing Designer and opening the image in your inspector sounds like no coincidence indeed. Also a 14 000 pixel image definitely takes a toll, since I assume it has to be actually created from the raw vector data on the spot. However strange you can't reproduce the actual copying issue. Reducing the PPI is definitely an option, thanks! However would be very interesting to think of elegant universal fixes for this from dev side. What comes to mind is caching the png but that'd take tons of RAM - disabling specific pasteboard representations. I'll try around and see if I can reach a state of the program where copying shows no loading behaviour, like in your case. If I manage that I'll check where the difference to my usual workflow is. Is there anyone from the staff who can shed some light on how things are copied and where the bottleneck could be?

Hey Walt, thank you for a swift and warm welcome. It's true. In the hurry I mixed up CMD + C and V. I mean CMD + C. It only happens on the action of copying, once the object is copied, pasting is without any interruption. Regarding the vector graphics: Understand it's nicer to reproduce this way. I attached an affinity designer file with one single artboard including some vectors. The content in this file does not include as many individual paths as the real ones, but it still happens for me. With this file, it's reproducible when copying the full art board. copying_issue.afdesign

Hello everyone, ran into this many hundreds of times in the past months - since I'm using the product. Thought I might give sharing this here a try. Affinity Designer Yes! Yes! Every time! It's slightly less when I copy the same content to a copy in fresh document, but still happens. If you cannot provide a sample document then please give an accurate description of the problem for example it should include most of the following: Ventura, M1 Max, 64GB of unified memory 2TB Storage Acceleration ON Long load on copy of relatively complex segments/objects of file Reproduce: Select vector object, CMD + C, Multi second loading starts, app becomes unresponsive Screenshots (very handy) or a screen capture/video. No unusual hardware. Happens with normal MacBook Pro internal display as well as externals Happens since a few months, nothing changed I use rather complex vector graphics that I can not share due to a project not being finalised and releasable yet. However it should be reproducible with any rather complex vector object. I fully understand this may be due to technical limitations of the current implementation, however similarly complex vector files in illustrator do not show this strongly interruptive behaviour. It majorly slows down the flow of working with complex graphics. copying_issue.afdesign