Jump to content

Stuck "loading document" on Monterey and Ventura; load time not improving over time


Megnusin

Recommended Posts

Yesterday, I reported Designer 2.2.0 getting stuck loading a document. Shortly before then, a pinned post was published, tying the issue to macOS Sonoma. I'm experiencing the issue on Monterey on a 2015 MacBook Pro as well as on an M2 MacBook Air that's still running Ventura, not Sonoma.

Additionally, the pinned post suggest the issue will resolve itself if the document is left to fully load. In my case, I'm still waiting up to 15 mins for the document to load after having already let it load completely yesterday. The load time is not improving.

It's suggested the issue is related to use of iCloud. The document has spent some time on iCloud Drive, but I've since moved it back to local (internal) storage without seeing any change in load time. I've also made a copy which hasn't touched iCloud with no improvement in load time.

It's also been suggested the issue relates to embedded images. This seems to be accurate in my case. I've saved a third copy of the document with all embedded images and all snapshopts deleted (to truly remove the images). Load time improved to near instant and the file size is down from 261 MB to 47 MB.

Finally, in addition to taking a long time to load, I've noticed it takes a similarly long time to save the affected documents.

Here are the troubleshooting details:

MacBook Pro early 2015

  • macOS Monterey 12.6.8
  • Affinity Designer 2.2.0 (installed via AppStore)
  • 8GB RAM
  • no antivirus
  • iCloud Drive enabled
  • document saved locally on internal storage
  • browser only other app open in addition to Designer (500 MB memory use; <10% CPU use)
  • Affinity uses 16GB of memory and 60-100% CPU while loading and saving affected documents

MacBook Air M2:

  • macOS Ventura 13.2.1
  • Affinity Designer 2.2.0 (installed via AppStore)
  • 8GB RAM
  • no antivirus
  • iCloud Drive disabled
  • document saved locally on internal storage
  • Affinity uses ~16GB of memory and 90+% CPU while loading the affected document

The document (original copy):

  • File size is 261.3 MB
  • Created in Designer 2.1
  • Contains embedded images (~100 of which ~40 unique)
  • No linked resources
  • Snapshots used extensively (100+)
  • 13 artboards
  • 12 fonts

I can't share the documents publicly, but Serif staff are welcome to get in touch for a copy to troubleshoot.

Edited by Megnusin
Updated troubleshooting details
Link to comment
Share on other sites

I assume this issue is different from the more widespread Sonoma issue.

Are there any linked resources (not embedded) used by this file? If so, did you move the resources off of the cloud when you tried moving the document off?

I experienced a long load time issue early in the 2.2 beta cycle but I haven't experienced it since July. The issue was repeatable by me but not by Serif, presumably due to the cloud config.

https://forum.affinity.serif.com/index.php?/topic/188533-opening-some-21-documents-in-22-takes-a-very-long-time/

Good luck

Link to comment
Share on other sites

Quote

I assume this issue is different from the more widespread Sonoma issue.

I don’t think so. This issue fits the description and is concurrent with the other reports.

Affinity 2.2 was released on September 28, two days after macOS Sonoma was released. I think the tie to Sonoma is mistaken and that it's likely just a bug in Affinity 2.2 itself.

Quote

Are there any linked resources (not embedded) used by this file?

There are no linked resources in the document.

The document was saved as a new file that was never synced with iCloud, and when placed on a separate computer with iCloud disabled, the issue still occurred. I don’t believe iCloud is the culprit.

Quote

Good luck

Thanks.

Link to comment
Share on other sites

  • Staff

Hi @Megnusin,

Thanks for the file.

Looks like this is more related to Snapshots.  I just deleted all of the snapshots, resaved and the file opened instantly.  

I've double checked this with QA as while the file opens in under 3 minutes for us, it does appear to be taking longer than we'd expect.  So I've logged this with the Developers :) 

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.