Jump to content
You must now use your email address to sign in [click for more info] ×

PDF export hanging the Publisher


Recommended Posts

I have fairly powerful computer with latest Publisher Windows. When I try to download
certain 20-30 page PDF documents for editing the Publisher just hangs. It can be left there
for hours and nothing ever happens.

That is very annoying. As Publisher is x64 product opening 20-30 MB PDF should not be an overkill.
I believe that there is something crashing in Publisher in such cases and thus this is a bug. It just
cannot be "out of resources" as process explorer shows 90% CPU and 10+GB of RAM available as free.
If need be I can provide one of the PDFs in question for your inspection.

I'd love to get this resolved.

Link to comment
Share on other sites

And of course it is PDF IMPORT not export...

anyhow, one of the files is here. It is 20 cards (1 card / page) for a new board game. 88x63 mm. Not really big as it's only 20 MB.

Now I have waited for 65 minutes for Affinity to open it. What happens is that Publisher.exe private bytes and working set (memory allocation) grows by some 8MB jumps or so. 
At this point it says 5.2 GB of private bytes and 5.0 GB for Working set. It started with about 1GB.

Memory leak? Crash in the system? This can not be normal.


Link to comment
Share on other sites

@multis I checked your PDF in Acrobat for X-4 conformity and Preflight showed some problems like having TrimBox and ArtBox at the same time, no OutputIntent, missing glyphs etc. pp. For more details see the screenshot (sorry only in German). After that I tried to convert to X-4 with ICC US Web Coated (SWOP) v2 (just to have one) and Voila! the file opened within a minute.

Conclusion: Something is going wrong when exporting from Scribus or APublisher has problems with the data. If you can export from Scribus again I would try with X-4 option (if possible). Attached the "repaired" PDF.

P.S.: The latest beta ( of APublisher won't import as well.




Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed

Link to comment
Share on other sites

  • 1 month later...
  • Staff


Thank you for reporting a problem using 1.7.x . It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script.

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the current 1.8.3 release build.

Patrick Connor
Serif Europe Ltd

"There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self."  W. L. Sheldon


Link to comment
Share on other sites

This topic is now closed to further replies.
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.