Infinity saves

[km.au]

With some documents, does anyone else hit a wall where after like 200 pages of linked content, Affinity gets stuck on 10gb+ of RAM, 25% CPU and just gets stuck on saving for hours.

It doesn't crash, but it doesn't save or the UI doesn't change. The document is usable but unsavable when becomes too many pages.

[Gabe]

Hi @km.au,

Can you attach the document in question and steps to reproduce the issue?

[uneMule]

Bonjour @km.au
si cela peut vous aider, je viens de créer un document de 300 pages avec images (avec lien) et textes dans le gabarit et effectivement ça rame.
L'affichage de la palette de pages ralenti beaucoup et surtout le contrôle en amont qu'il convient de configurer autrement qu'en mode dynamique.
Par contre aucun soucis pour l'enregistrement du fichier. Très rapide.
J'utilise un portable core i7 (assez ancien) un disque SSD et 16 Go de Ram, windows 10 dernière mouture.
Bon courage.

Hello @km.au,
if it helps, I just created a 300 page document with images (with link) and text in the template and it's actually working.
The display of the page palette slows down a lot and especially the preflighting that needs to be configured differently than in dynamic mode.
On the other hand, no worries about saving the file. Very fast.
I use a core i7 laptop (quite old), an SSD disk and 16 GB of Ram, Windows 10 last version.
Good cheer.

Translated with www.DeepL.com/Translator (free version)

[km.au]

Opening a 3mb Affinity pub file now....20gb of ram and 100% cpu for 30 mintes

 

It's borked.

[Gabe]

You can use this private link to upload your file: https://www.dropbox.com/request/dGr0zGOwW5VhNk2pzmbf . If not, I'm afraid we can't really investigate a document related issue with no document. Sorry. 

[uneMule]

Hi @km.au , hi @Gabe
lorsque j'ai fais le test de mon côté, il est certain que la ressource demandée a été importante et les ralentissements patents.
Je n'avait pas ressenti ça depuis longtemps en faisant de la mise en page. Le document n'étant pas vraiment complexe de surcroit. Une image identique dans tout le document. Un bloc de texte 2 colonnes, non chainé.
When I did the test on my side, it is certain that the requested resource was important and the slowdowns were obvious.
I hadn't felt that way for a long time when I was doing layout. The document wasn't really complex either. An identical image throughout the document. A 2 columns text block, not chained.

[km.au]

Hey Gabe, sorry for the late reply.

We are creating reports and consultants have been sending us their reports in PDF format. We've had affinity import these pdfs into a master afpub file, so like 100+ pages of native content and 70/80 pages of just linked PDF pages.

This is where the problems arise.

It can happen as above (uneMule's) experience.

 

To test, if you load any multipage PDFs into Affinity Publisher (over 100 pages it becomes most obvious) there is some sort of a memory leak + slowdown.

The program bogs down so much that it is practically unusable.

 

In the end we just create our content in Affinity Publisher and use Adobe Acrobat for merging in consultant PDFs and further editing as it handles 100+ pages perfectly and no memory leaks.

 

[km.au]

@Gabe

Attached is a reproducible file. This one, while I can't get it to 32gb of RAM like our internal reports, it shows how there is a serious bug with Affinity.

 

 

Just opening this test file, it will lock up a computer and it's a 3mb PDF...

 

 

Downloads.zip

[Gabe]

Thanks. Issue logged, 

[km.au]

Hi Gabe,

It looks as if this is resolved in 1.9.2.1035.

 

Thanks very much for this as it allows us to write huge documents now with multiple PDFs. Absolute lifesaver.