Page 1 of 1

Problem with large postscript file

Posted: 2009-03-26T07:39:31-07:00
by tsdineen
I am running into a problem with display that appears to stem from ghostscript. Running display on this file causes the below results. If I run gs by itself, I get the same error, but I can display the output file. I have little knowledge of the postscript language, and only maintain the image tools. Is there a way to surpress this error? If not, can you point me in the direction of what to look for in the ps file that may be causing this error?

Thanks,
test wrote:testnode>display -verbose /tst/dev/tst-v930/gdrv/testbps/tilzpsco.bps

"gs" -q -dQUIET -dPARANOIDSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=500000000 -dAlignToPixels=0 -dGridFitTT=0 "-sDEVICE=pnmraw" -dTextAlphaBits=4 -dGraphicsAlphaBits=4 "-r85.1099x86.1245" -g640x862 "-sOutputFile=/tmp/magick-XXnbQPyr" "-f/tmp/magick-XXOu4x3K" "-f/tmp/magick-XXJBxUy4"
Error: /typecheck in --restore--
Operand stack:
--nostringval-- (\377\377\377\000\000\000|\225\312\377\300\313\377\302\314\377\367\371\377\321\331\377\360\362\377\350\354\377\340\346\377\331\337\377\311\323) true true
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop 1904 1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- 1834 3 3 %oparray_pop --nostringval-- 1818 3 3 %oparray_pop --nostringval--
Dictionary stack:
--dict:1155/1684(ro)(G)-- --dict:0/20(G)-- --dict:94/200(L)--
Current allocation mode is local
Current file position is 13572445
GPL Ghostscript 8.62: Unrecoverable error, exit code 1
"gs" -q -dQUIET -dPARANOIDSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=500000000 -dAlignToPixels=0 -dGridFitTT=0 "-sDEVICE=pnmraw" -dTextAlphaBits=4 -dGraphicsAlphaBits=4 "-r85.1099x86.1245" -g640x862 "-sOutputFile=/tmp/magick-XXnbQPyr" "-f/tmp/magick-XXOu4x3K" "-f/tmp/magick-XXJBxUy4" -c showpage
Error: /typecheck in --restore--
Operand stack:
--nostringval-- (\377\377\377\000\000\000|\225\312\377\300\313\377\302\314\377\367\371\377\321\331\377\360\362\377\350\354\377\340\346\377\331\337\377\311\323) true true
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop 1904 1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- 1834 3 3 %oparray_pop --nostringval-- 1818 3 3 %oparray_pop --nostringval--
Dictionary stack:
--dict:1155/1684(ro)(G)-- --dict:0/20(G)-- --dict:94/200(L)--
Current allocation mode is local
Current file position is 13572445
GPL Ghostscript 8.62: Unrecoverable error, exit code 1
display: Postscript delegate failed `/tst/dev/tst-v930/gdrv/testbps/tilzpsco.bps': No such file or directory @ ps.c/ReadPSImage/742.
LOGO GIF 640x480 640x480+0+0 8-bit PseudoClass 256c 37.4kb
logo:=>LOGO LOGO 640x480 640x480+0+0 8-bit PseudoClass 256c 37.4kb

Re: Problem with large postscript file

Posted: 2009-04-01T04:47:04-07:00
by tsdineen
I might add ghostscript doesn't fail to bring up the image in a normal state, only when display tries to bring this file up.

Re: Problem with large postscript file

Posted: 2009-04-01T05:43:27-07:00
by magick
Can you post a URL to your Postscript image? We need to reproduce the problem before we can comment.

Re: Problem with large postscript file

Posted: 2009-04-02T11:36:26-07:00
by tsdineen
The image can be found here: ftp://ftp.sas.com/outgoing/tilzpsco.tar.gz. You won't be able to see the file if you go to the ftp site, but you should be able to pull it with the url provided.

Re: Problem with large postscript file

Posted: 2009-04-02T12:04:18-07:00
by magick
ImageMagick relies on the status of Ghostscript. If the status shows failure, ImageMagick aborts. We do not anticipate changes to this workflow because if Ghostscript fails we do not consider any pixels it creates as reliable.

The best option would be to either fix the Postscript file or file a bug report with Ghostscript.