Skip to main content
Participant
July 31, 2012
Question

Long postscript document crashes at printer

  • July 31, 2012
  • 1 reply
  • 941 views

I am printing out long documents, some over 100 pages.  I have an in-house application where I generate the PS file based on data we have.  The user chooses criteria and then we get a print out.  If the document is smaller then it prints the entire document fine.  If I get over a certain number of pages, 35-40 maybe, printing consistently stops in the same spot.  If I modify the ps file to be shorter, then the file prints fine.  If I do a simple loop to print 100 pages it prints fine.  Sometimes I get an offending command, which looks like it cut off part of the command, like 'how' instead of 'show'.  If I modify my program to send 10 page groups instead of all at once then it prints fine.  It seems like it's filling a buffer or something first?  Any ideas?  Here's a link to the file.  https://dl.dropbox.com/u/2430447/SPL0333842

This topic has been closed for replies.

1 reply

Mr__Horton
Inspiring
August 8, 2012

Your file distilled into a complete pdf booklet (107 pages) after I removed the printer escape characters that had been prepended and appended.

In looking at the PostScript code the structure of the code layout is part of the problem:

the occurrance of "-2 vmreclaim" several times per page, followed by a redefinition of the user procedures could be cleaned up so that the user procedures are defined once in the prolog of the document and the "-2 vmreclaim" statements are removed altogether. "-2 vmreclaim" turns off the automatic garbage collection, normally this would be done for interactive or monitoring functions, but in this context I don't know why that would be of benefit.

After commenting out the "-2 vmreclaim" like "%% -2 vmreclaim" throughout the document, distiller rendered the program much, much faster, and I would guess that your printer will render it completely and faster as well.