The attached file, when processed with gs8.64 generates a Windows XP "gswin32c.exe has encountered a problem and needs to close" error dialog box. Ghostscript itself does not print an error message. The command line I'm using for testing: "\Program Files\gs\gs8.64\bin\gswin32c.exe" -sOutputFile=Test.tif -sDEVICE=tiffg4 -dNOPAUSE -dNOSAFER -dBufferSpace=120000000 -dMaxBitmap=40000000 -dNOCIE -r400 "2007-0030-A502-Vertical Circulation.pdf" The customer reported that -r800 was required to make the file fail, but my testing shows it also failing at -r400 (though it works -r300). The equivalent command does not fail under Mac OS X.
Created attachment 4808 [details] 2007-0030-A502-Vertical Circulation.pdf
*** Bug 690302 has been marked as a duplicate of this bug. ***
I am able to reproduce a Segmentation violation at 800 dpi. This happens during clist playback, so I will investigate it and reassign it to someone else if I possibly can (but I doubt it).
As of rev 9858 this no longer segfaults for me at 400 or 800 dpi (8.64 does). Assigning to Marcos to see if he can find a patch with 'search-svn-revs'
Tried to reproduce on my Win XP Pro SP3 (vmware on Mac) + VS2008 Express SP1. 8.70rc1 (r9909) doesn't show this symptom. Also tried with 8.64. 800 dpi always failed with access violation on gxclip.c line 257. 400 dpi was more cranky. It only failed at first try after clean build just after machine reboot. (sounds crazy but this is what happening on my machine)
It is likely, based on Masaki's testing that this difficult to reproduce issue has been fixed by some of the valgrind warning fixes and fixes to some of the SEGV bugs since the code of the original report. Closing as FIXED. Thanks, Masaki !
I'm confused masaki wrote: "800 dpi always failed with access violation on gxclip.c line 257." why is this fixed?
The failures were with 8.64. Once the customer upgrades to 8.70, if they still see problems, we can re-open (or open a new bug).
Sorry I did not read masaki's description correctly, disregard comment #7
Changing customer bugs that have been resolved more than a year ago to closed.