Bug 699815

For me this seg faults (on Windows 32-bit) in clist playback, so assigning to Ray in the first instance.

(In reply to frralt102 from comment #0)
> (The attached PDF was obtained by executing the following command, where the
> original PDF -- of the same name -- was generated by pdflatex.
> 
> /opt/local/bin/gs -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dQUIET -q
> -sDEVICE=bbox -r72 -dLastPage=1 './36275aec95788800a43a3a859f633fd9.pdf'
> 
> For context: this PDF was generated by the LaTeXTools plugin (to the
> Sublimetext editor) via pdflatex to generate live inline-math previews.
> Similar commands will fail for all such generated PDFs when the final output
> image size is large enough. Setting -r600 or less seems to allow success for
> final output images that are not too large, such as the example here.)

I am experiencing the same bug in the same context, but just as a clarification, this command here doesn't actually generate or modify the pdf. It gets the bounding box information from the pdf, which is then used to compute the dimensions of the converted png (through the -g3733x1467 argument).

I can also confirm that this bug seems to occur only when the size passed to the device via -g is too large. Changing the resolution doesn't seem to affect it. Somewhere around 2.5k pixels is when it happens, though the aspect ratio seems to matter as well.

I apologize for the confusion(s): I admit that I'm far from an expert with this software, and I composed the bug report pretty hastily.

Still, I'm happy to help if I can: for example, I can easily generate some additional PDFs that are similarly afflicted.

Created attachment 15951 [details]
segfault causing pdf

I think I'm having the same issue with the attached PDF.

gs -q  -dBATCH -dNOPAUSE -sDEVICE=pngalpha -dUseTrimBox  -dQFactor=1.0  -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -dFirstPage=1 -dLastPage=1 -r300  -sOutputFile="testingout" "testing.pdf";

Let me know if this is indeed the same issue and if I can do something to debug here.
This issue starts with 9.24 for me as well 9.25 also has the issue. 9.23 and below work fine.

(In reply to na from comment #4)
> Created attachment 15951 [details]
> segfault causing pdf
> 
> I think I'm having the same issue with the attached PDF.
> 
> gs -q  -dBATCH -dNOPAUSE -sDEVICE=pngalpha -dUseTrimBox  -dQFactor=1.0 
> -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -dFirstPage=1 -dLastPage=1 -r300 
> -sOutputFile="testingout" "testing.pdf";
> 
> Let me know if this is indeed the same issue and if I can do something to
> debug here.
> This issue starts with 9.24 for me as well 9.25 also has the issue. 9.23 and
> below work fine.

I don't believe this is the same problem, though its difficult to be certain. However this file and command line does not seg fault for me, whereas the originally reported file does, as described.

This appears to be a problem caused by the device subclassing (and some seriously ugly code in the pngalpha device), so I'm taking this one on.

Note that you can probably avoid the problem by simply not using -dFirstPage and -dLastPage. If the problem goes away when you drop those command line switches, then its the same problem.

Fixed in commit 04333a6f1344df6b5069880cafe7b190d0984601

I can't say for sure that it fixes the second case, since that didn't seg fault for me.

*** Bug 700313 has been marked as a duplicate of this bug. ***

*** Bug 700315 has been marked as a duplicate of this bug. ***

*** Bug 700339 has been marked as a duplicate of this bug. ***

(In reply to Ken Sharp from comment #7)
> Fixed in commit 04333a6f1344df6b5069880cafe7b190d0984601
> 
> I can't say for sure that it fixes the second case, since that didn't seg
> fault for me.

Hi Ken,

Thanks for putting through a fix on this, we appear to have the same issue with 9.26 and the `-dLastPage` option.

Do you happen to know the typical timeframe on a new release going out with this bugfix, or should we look at rolling back the `gs` version?

Regards,
Elliot

(In reply to elliot.cm from comment #11)

> Thanks for putting through a fix on this, we appear to have the same issue
> with 9.26 and the `-dLastPage` option.

If its with 9.26 its a different problem, see bug #700315 I think.

 
> Do you happen to know the typical timeframe on a new release going out with
> this bugfix, or should we look at rolling back the `gs` version?

Ghostscript is normally released twice per year, once in March and once in September. Serious security problems will cause us to issue an interim release, but otherwise that's the schedule.

We have a PDF file with multiple pages. We need to rasterize any page from that PDF file. GhostScript version 9.26 is not working, but version 9.25 works fine. 

Please fix this issue with next update.

Alex, you should test with the current version on git, or at least with the
release candidate when it becomes available (subscribe to gs-devel mailing
list to be notified). If your condition is different to the one that has been
fixed, and is not fixed in the current git source version, we cannot assure
you that your condition is fixed (you haven't added a problem file and
command line to this bug).