blwfish

Happy to do that, although it will probably have to wait until I get to a faster connection. I just tried on my hotel connection and it's crawling along at a bit less than 200KB/sec, which would take a really long time.

I have more information on this. (I'm the same person who reported it originally, I'm having email trouble.) Using a large file with MANY images in it, Publisher is consuming about 750MB "at idle." When I load the file, it goes up to about 1.7GB - that's to be expected. If I then scroll through the book, I can see the memory footprint get bigger and bigger as I cross more pages. On my 40MB desktop system, it was not really a problem to use 33GB. However, scrolling through 55 pages on my 16GB MacBook Pro DEFINITELY IS A PROBLEM as it blows out Publisher's footprint to around 17-18GB. That of course is 10 pounds in a five pound sack, so there's flour all over the floor. If I close the file, memory footprint goes back to about 750-800MB within a few seconds. If I then load the file again and scroll, it repeats the behavior. For grins I loaded the file and then let it sit and do nothing. Of course, the footprint stays static in that case. This behavior is entirely repeatable or at least it was whilst I was on the plane this afternoon. If I let this continue, it will eventually lead to lots of spinning beachballs (that's how I noticed). I've been working around it by frequently saving, closing and reopening. Rather than scrolling to the work site within the book, I Document->Goto Page which seems to avoid the problem. This of course is only a workaround and it's only as good as long as I refrain from scrolling, which as you can imagine is not easy. This system is a Macbook Pro 14,2 with 16GB memory. It too is running Mojave.