Bug 693853 - segfault/floating point exception with or without -dNOGC
Summary: segfault/floating point exception with or without -dNOGC
Status: RESOLVED DUPLICATE of bug 693921
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Regression (show other bugs)
Version: 9.07
Hardware: PC Linux
: P4 normal
Assignee: Chris Liddell (chrisl)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-11 16:19 UTC by David S
Modified: 2013-05-07 09:18 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---


Attachments
case 1 (19.59 MB, application/pdf)
2013-04-11 17:17 UTC, David S
Details
case 2 (12.32 MB, application/pdf)
2013-04-11 17:18 UTC, David S
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David S 2013-04-11 16:19:08 UTC
also seen on windows. here i'm testing on linux:

i'm convering these odd PDF files to JPG with these command line arguments: 
-dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -r150 -sDEVICE=jpeg -dJPEGQ=90 -dNumRenderingThreads=4 -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -sOutputFile=/tmp/page-%04d.jpg

and have been experimenting with and without the -dNOGC option (for a 10-20% speedup). but seems like there's a regression in 9.07:

case 1 with this file: http://sicnarf.com/wp-content/uploads/2013/04/verteiler_kw_16_2013.pdf
9.06: no problem
9.06 with -dNOGC: no problem
9.07: no problem
9.07 with -dNOGC: seg fault

case 2 with this file: http://sicnarf.com/wp-content/uploads/2013/04/crash_ghostscript_saturn_14_flash_v2.pdf
9.06: segfault
9.06 with -dNOGC: segfault
9.07: no problem
9.07 with -dNOGC: segfault
Comment 1 Chris Liddell (chrisl) 2013-04-11 16:30:11 UTC
Please attach the example files to the bug report (that way we can be sure of accessing them in the future).

Thanks.
Comment 2 David S 2013-04-11 17:17:08 UTC
Created attachment 9507 [details]
case 1
Comment 3 David S 2013-04-11 17:18:09 UTC
Created attachment 9508 [details]
case 2
Comment 4 Chris Liddell (chrisl) 2013-05-07 09:18:50 UTC
This is already fixed.

*** This bug has been marked as a duplicate of bug 693921 ***