Affinity Publisher V1 PersonaBackstore.dat grows beyond 100 GB

[saladknown]

I've been using AP V1 for a while now to create a catalogue. It's not small (~180 pages with maybe 400 images), but not crazily large I would suppose. I recently noticed that when using AP, my C harddrive will run completely out of memory when leaving AP open for too long (not even using it, just being opened with that project). I realized that it's the somewhat known "PersonaBackstore.dat" file which keeps growing and growing.

I have 16 GB RAM on board (yes, not too much, but assuming that everything in PersonaBackstore.dat should fit in RAM, I don't think it matters if I would even have 64 GB of RAM).

I've read through several threads here in the forums and could not find a definitive answer. Someone wrote that it should (confusingly) help, to set all images to embed and not link.

Isn't there any option to set the desired viewing quality, so AP doesn't render everything super high when editing (only could find the Bilinear vs. Nearest Neighbour setting)? Or to only render X current pages?

[saladknown]

Ok, I'm seriously confused on how Affinity Publisher works and manages its internal stuff. Just out of curiousity, I saved my project as an .afpackage. When I open this one, I do not have the issue with the PersonaBackstore.dat file. It stays at 0 kB. Moreover, editing the project is WAY more responsive than it was before. I stored it once again as an .afpub file and the new size (so .afpub -> .afpackage -> .afpbub) reduced from around 104 MB to 8 MB. Opening the new .afpub also seemingly resolved my PersonaBackstore.dat issue.

While I'm kinda happy that this seems to be a workaround, I have zero idea why and how. And why.

[NathanC]

Hey @saladknown apologies for the late reply,

The Affinity apps use as much memory as required, when the maximum physical RAM usage is hit, I believe it starts caching/storing elements in the personabackstore.dat file. I've seen it previously with a specific file where Publisher will gradually fill up this file despite being completely idle which was caused by a specific object/image within a file that was corrupted, so it's possible that this was the case with your document and re-packaging the file has somehow repaired the file.