Export to PDF crashes everytime. Grrrrr

[Aftermath13]

I have a 326 page document, only 29mb, has 1,000+ images that are all linked.

Im trying to export to press ready PDF, gets to about 70% and then i either get the

error occured when exporting message or it just closes the program.

Very frustrating, needs to go to press asap.

Publisher V2.6, Windows 11,  Asus Tuff. Intel i5-8300CH, 8GB RAM.

[Alfred]

Welcome to the Serif Affinity Forums, @Aftermath13.

Have you tried exporting a selected page range?

[Aftermath13]

@Alfred no i havent, will give it a try.

Shouldnt have to though, why cant it do it in one file ?

Not a large file at all

[GarryP]

Exporting part of the document will give you some idea of whether the document as a whole has a problem or just some of it.

If part of it exports correctly then you can use that information to try and narrow-down the possibilities by exporting different parts to find the part which doesn’t export correctly.

Then you can look at that part to see if you can see any possible problems by removing layers until it exports correctly.

Once you can do that you will have found where the problem is and can tell us more about it.

[Alfred]

It may be nothing to do with file size. There could simply be something 70% of the way through the document (a page, or just one object on a page) which is causing the PDF export procedure to choke.

[Aftermath13]

@Alfred @GaryP 

ok, i broke the export down to 50 pages each,

failed on the 250-300, so i then broke that block down to

10 page blocks, and all have exported ok, will keep trying diff numbers

of blocks to see if i can find the page/pages where the problem is

[Alfred]

12 minutes ago, Aftermath13 said:

failed on the 250-300, so i then broke that block down to

10 page blocks, and all have exported ok

Very odd!

[GarryP]

2 hours ago, Alfred said:

Very odd!

Indeed.

If the export fails when exporting pages 250-300 but is okay when exporting each ten-page ‘block’ of those pages then that suggests to me that there might be something which ‘straddles’ either page 250 or 300 which could be causing the problem, maybe something on a master page, or perhaps a text frame flow issue?