blw

The file is 1.7GB in size before save as and 1.62GB in size after. Not materially different, I'd say.
> Are you on a Mac?
I did post this in the "beta on Mac" forum, but yes I'm on an iMac 17,1 with 40GB memory.
> For speed (and other)  reasons Affinity files are quite heavy
I get it. I did say - in my original note: "the system was definitely behaving and if that's normal, so be it."
> Why RAM is there to use it. Otherwise it isn’t necessary.
I know that. I've worked on Unix VM systems - professionally - so I have a fairly decent idea of what's going on. I neglected to mention that without the large Publisher footprint, the rest of my system readily grows to ~28-30 GB. So Publisher probably is displacing pages that would be productively going to other uses, albeit perhaps at lower priority. MacOS didn't go off and compress a bunch of stuff, so it would seem that the memory pressure is light, but present.

I just noticed that Publisher had sucked down a full 33GB of memory - I have a 40G system. I only noticed because some of the stats on the system seemed to be going kind of nuts. The system was definitely behaving and if that's normal, so be it. My main project has MANY images, mostly large ones, so it's not 100% surprising to eat a lot of RAM. But 33G is a lot...
Quitting and reloading the same file yields a memory footprint of slightly under 4GB, so I'd say it's virtually certain that something was leaking memory within the process. Judging by the magnitude and what I've been doing with the program, I'd guess it would have to be related to images. Anything I can do to better identify this?

> See: Affinity Publisher Beta Help > Publishing and Sharing > PDF Publishing > Publishing PDF Files:
Oh. Maybe then I mean better indexing. I looked for export - which of course is the command involved.

In the intervening couple of weeks, I've upgraded to .162 and things appear to be quite different now. Although scrolling from newly loaded file does grow the memory size, it now grows only so far and then stops growing. I can't get my file to exceed 22GB now, even on my 40GB system - even though the file is now materially larger than it was back when I reported the bug. I've been scrolling back and forth all day and it's still sitting at about 21GB. Previously this would just go much further (over 33GB as previously noted). Something's been fixed, although I don't see a reference to such a thing in the release notes.

Sorry to be so dense, I must have just missed it. On my Mac, it has them defaulted to Apple-pg up/dn, which I'd have never guessed. I've got it sorted now, thanks.