[gs-bugs] [Bug 690351] PDF does not render on Page #7. Tried on Both Linux and Windows

bugs.ghostscript.com-bugzilla-daemon at ghostscript.com bugs.ghostscript.com-bugzilla-daemon at ghostscript.com
Sat Mar 21 10:01:18 PDT 2009


http://bugs.ghostscript.com/show_bug.cgi?id=690351

ken.sharp at artifex.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P3



------- Additional Comments From ken.sharp at artifex.com  2009-03-21 10:01 -------
The file does open, I believe, though I haven't tried waiting long enough to
find out. Its clearly going to take a very long time. The action of
interpolation is described in the reference manual as 'device dependent', so its
pretty much up to us what we do. 

I did debug the file and it is spending a lot of time in the interpolation code
(its a very big image), and the fact that turning off interpolation renders
quickly is a pretty big clue.

-dNOINTERPOLATE is described in the Ghostscript documentation in /gs/doc/use.htm

You can skip a page from the PDF if you wish, or you can disable interpolation,
both are described in the documentation. 

The PDF is basically valid, and renders quickly if you don't try and interpolate
it. As far as I can tell from a quick inspection GS does not 'stall' it simply
takes a long time to perform the requested operation. To add insult to injury,
the page in question also uses transparency, so there's another very large image
laid over the top of it and composited with it.

(Ray, I don't get the correct output with this page anyway, would you check with
the soft mask branch please ?)

The damaged font is a different issue, please note that it is not Ghostscript
complaining about the font, but Adobe Acrobat 9. A damaged font is very often a
good reason to abort a job as the PostScript font subsystem (which is the same
in many respects as PDF) is allowed to expect well-formed fonts and does minimal
checking in order to increase performance.

You asked for a work-around, you have one; use -dNOINTERPOLATE. I don't
understand why you are unwilling to use this, in the general case it makes no
difference since most images do not specify interpolation. Unless you want very
high quality output, turning off interpolation even for those images which do
specify it will make no significant difference to the output either.

I won't set this back to closed, I'll leave that for support to decide, though I
see no reason to describe this as a bug. I have, however set the priority back
to 3. P1 and P2 are reserved for Artifex commercial customers.





------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.



More information about the gs-bugs mailing list