File is large and crashes easily

[DKMusic]

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.

[Lee D]

The apps native formats file sizes aren't calculated based on the size of files embedded/linked or used in the document but are optimised for loading. Have you found the crashing to be when editing specific documents or performing certain tasks?

Can you use the following FAQ to check for the most recent crash report from your system and uploaded here for checking, this may narrow down a cause.

 

The Bug section is more form if you can replicate an issue within the app following a workflow that reproduces the issue each time.

[DKMusic]

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.

[DKMusic]

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

[DKMusic]

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?

 

[DKMusic]

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

[lacerto]

Obsolete.

[DKMusic]

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

[DKMusic]

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