DKMusic

In the example below, I need to add one to all numbers above 297. So 296 stays 296, but 308 becomes 309, etc. Is there any easy way to do this?

The crashes continue, even with embedding (which I shouldn't have to do). And not a single response from the team in the five weeks since I first posted my request. This isn't a hobby for me, it's a job. I can't afford to continue losing time and work. I vastly prefer APub to InDesign in every way for what I do... except for constant crashing that renders the program unusable. And I'm disappointed that none of my support requests in this regard have been answered. Professional software needs professional support. Unfortunately I have no choice but to return to InDesign. I hope this issue can be resolved in future versions.

Any response from the team would be greatly appreciated.

As I reported here, I've had constant issues with large RAM usage and crashing in Affinity Publisher. My primary usage is creating hymnals. They may be around 400-500 pages and contain perhaps 400 linked PDFs. I can share the file privately. At present I have to wait approximately 4 minutes for the RAM and CPU to settle down, and then it usually doesn't crash. If I try to do anything in the program before then, it crashes 100% of the time. I have this exact same issue on two machines. One is Windows 10, Ryzen 5900x, 64GB RAM, Publisher 1.10.5. The other machine is Windows 11, Intel 11th-gen i7, 64GB RAM, Publisher 1.9. I have no idea which of these specs are pertinent, or if there are additional ones needed. I've been trying to work around this issue for two months since switching from InDesign (quite happy to switch, I might add), and I am at my wits' end. Any suggestions would be greatly appreciated. Thanks.

I was really hoping I'd get a response from someone at Affinity regarding this issue, which continues to plague my work, even on 1.10.5. My current workaround is to wait approximately 3.5 minutes after opening, after which point the RAM stops increasing and the CPU drops from 40% to zero (I'm running a Ryzen 5900x... this is a pretty simple document.. so that CPU usage doesn't seem correct either). Sometimes it works to wait, sometimes it crashes anyways. And I doubt the problem is my computer, because I never experience this behavior in any other software, but this happens in APub on both my machines These constant crashes make it feel like Publisher is a great idea that isn't yet up to the task. That might not be a fair assessment, but that’s how it feels. As a user on deadline, I can't navigate these problems unresolved. I was thrilled to move away from InDesign, and I vastly prefer APub. InDesign has its problems too, but I've never encountered this sort of issue that stops my workflow dead in its tracks. Come on, folks, I don't want to go back! I will try posting on the bug forum as well. Can anyone from the development or tech support team weigh in, please? Thanks.

Thanks. If it is indeed a memory leak, what is to be done?

Yes, the files were created on the same machine I’m using APub on.

To a point, yes. When I open a document, it gradually creeps upwards for the next several minutes. I find it’s best to wait to perform any computationally significant functions until it’s done increasing. Today was the first time it crashed without me doing anything. I disabled hardware acceleration (but why though…) and lowered max RAM usage to 27 GB. When I did that, it stopped increasing when it hit 27 GB, then I was able to use the program without crashes (so far). Still, 27 GB seems ridiculous, and I’d like to find a solution if possible. Thank you.

Here's an example: A Mighty Fortress Is Our God_BH91_ns.pdf

Most PDFs are one page, sometimes two.

Thanks Walt. They are linked PDFs, music notation, not images. The PDFs themselves are pretty small. The final exported PDF of the entire document tends to be around 10 MB.

Here's a screenshot. Why is AP taking so much RAM?? This project is 300 pages, placed PDFs, nothing complicated. The program is unstable and crashes frequently. I have hardware acceleration disabled. When I did this, AP is still using 100% of the RAM I've allocated to it: 27 GB. Surely that can't be right.

Oops, I answered my own question! The setting I needed to turn off was for "PDF passthrough," further down in the list.

I've set my preflight profile to disable color mismatch warnings, but I'm still getting scads of them. What am I missing?

I have figured out how to place a rectangle with no stroke and no Phil, but I can’t figure out how to use that shape to cut out what I want.

Hi Paul, I’m still not understanding exactly how to do that. Where exactly would I find that function? Thanks.

In InDesign, exporting a several-hundred-page PDF, even with text-only passthrough PDFs in it, took several minutes. Sometimes as long as 10. But in AP, it takes literally 2–3 seconds. I've very curious to know why that would be the case. Apparently it has to do with how the two programs are using and rendering PDFs?

I turned on debugging and force-attempted an export immediately upon opening the file (not waiting for the RAM to load). It crashed, as expected, and I got this log: pdflib.log

Thanks @Lagarto. I did find what seems to be one solution: wait until the program is completely loaded into RAM before performing any functions in it. It looks like it's loaded pretty quickly, but it's no don yet... I turn on the Task Manager (Windows) and wait until the RAM allocation for AP stops increasing. That's helped with that particular exporting crash. If I have to complete the document in parts, I'll do that, but my hope was to use AP for all my professional work going forward. I'll turn on debugging as you suggested and post whatever pertinent info it produces. I want Publisher to work for me... Moderators, can I share my file privately for the development team to take a look, please? Best, Dan

A day later, I'm continuing to experience crashing, even on a Ryzen 5900x with 64 GB RAM. Surely this can't be right. My document is 380 pages but nothing particularly resource-intensive. I really, really want to leave InDesign behind. I really love the workflow of AP. But I've lost many hours of work over the past two days on crashes, which is totally unsustainable. I'd appreciate any insight the team could give on how to eliminate these crashes, thanks. e572e0b7-095a-41bc-a7ad-ad9e657b8294.dmp

Very frustrating. I'm trying to drag a spread from page 84 to page 120, and AP keeps freezing. Can't save, no crash logs, can't move forward. Help? Also, I find the file has ballooned to 270 MB. When I "Save as" instead of "Save," it's now reduced 24 MB. What is going on here?

Ok, I have a reproducible crash. I open a file set to RGB with lots of linked PDFs. Document Setup, set color to CMYK 8. Then when I click on "Export..." it crashes. Dump file is attached. 58950f05-d406-490b-ba12-b1b9c174a883.dmp

Thanks Lee. Predictably, it hasn't crashed since I posted. Of course... 🙄 I've been successfully working on this file on another computer, a more powerful desktop. However, it's taking literally 5 minutes to open the file on my laptop. It's an i7, Xeon processor. Shouldn't take that long, right? I have also found that if I save a new version using "Save As," that file is much smaller. Perhaps 130 MB instead of 170. That doesn't seem right either. Should I still upload any diagnostics? I can't post the file publicly here, but I can send it to a development team member privately.

I've been working on a 300-page document. Each page has one or two linked PDFs. The Publisher file is about 165MB and is prone to crashing. Have I done something wrong? That's a huge file considering the PDFs are linked, not embedded. Right? EDIT: I'm going to post this on the bug sub-forum, as it seems to be a better place for it.

Thanks! Much to learn...