cleversprocket

I've found that if I work in a file straight through, meaning I don't close the program and reopen it, then the software doesn't have a memory issue. However, if I duplicate a file or create a new document and add pages from a different document then the software consumes a huge amount of memory. For instance, I created a 191 page document made up of placed pages from other documents and the memory went up to 7GB which was very manageable on my machine and I didn't experience any lag. But when I created a document and imported only a quarter of the pages from the 191 page document using "Add pages" the memory shot up to 13GB and the software became unbearably laggy. This was from a fresh launch of the software and no other documents were open.

I've found a workaround for this issue. I took my 188 page book and quartered it into 4 files. Each file consumes roughly 6GB of memory, which is more than manageable for my machine. With that said I don't think it's a memory leak because all 4 files add up to roughly the same amount of memory consumption to the original file. To assemble all 4 files into one book I export each file as a PDF and import all the PDFs into a new file by using "Document" > "Add pages from file". The new file with all the pages imported consumes a fraction of the memory. I haven't imported all 4 PDFs yet but I have imported 2 of them and it's only consuming 2.3GB. @Sean P that invalidates the assumption that a file heavy with images is causing the massive memory allocation. I'm a developer and I'm guessing the issue is caused by the individual objects that make up each spread. I'd argue objects should be released from memory if they are not needed for the page being worked on. I really like this software and I consider myself an early adopter and willing to make sacrifices to my workflow as the product grows. However, if this issue is not addressed in the near term I'll have to abandon it for InDesign.

To follow up on my last post, I split the file into 2 files hoping it would solve the memory issue but it didn't. I have the file open and idle and I'm watching the memory consumption climb using Activity Monitor. My guess is there is a memory leak somewhere.

Hi @Jon P sorry but I no longer remember which file caused it. I've since moved on.

I just encountered this same problem. Publisher is using 20GB of memory! When I open the file the laptop's fans kick on high and the battery is eaten alive. The file I'm working in is 60MB on disk and 188 pages. Nearly all the pages are linked documents and none of them are that large. Most of the graphics are fairly simple vectors. I have 64GB available storage on the SSD.

I experienced this same problem today using a Mac and Publisher 1.8.1

This issue just happened to me on a MacBook Pro using 10.14.6. Conditions: Affinity Designer updated to 1.8.1 Arranging layers was working. I did something that made all the view palettes condense down into one frame. I don't know what I did but it seemed like a bug. I then noticed I couldn't arrange layers.