Description of Problem: Using ghostscript to distill postscript produced by Windows/Adobe Postscript printer drivers, I've found that some documents cause ghostscript to enter some kind of race condition where it consumes 100% CPU without actually appearing to do anything useful. Version-Release number of selected component (if applicable): ghostscript-5.50-17 How Reproducible: I can provide a document that will tickle this bug, however, I am not able to post it publically because it contains private information. I will be happy to send the document to whomever is assigned this bug. Steps to Reproduce: 1. 2. 3. Actual Results: Expected Results: Additional Information:
Having checked with our legal eagles I'm sad to report that I can't even send the document privately because of the UK Data Protection Act. I'm going to play around with it and see if I can remove the private data and still reproduce the bug, failing that, what can I do to provide you with enough information to be able to investigate?
This is not surprising. PostScript is a production language, and as such, is succeptable to the halting problem. Some documents don't ever finish. A brief example follows: %!PS-Adobe-2.0 /loop { 1 add dup == loop } def 1 loop Without an example document which _should_ finish, but does not, I am closing this.