Legacy ImageMagick Discussions Archive

Attached is a patch that will let the pdf coder use the basename of the output file as the PDF title rather than the entire path of the output file. It appears to work fine on Mac OS X 10.6.5, unsure if it will work on other OSen (mainly the "#include <libgen.h>"), it may need some work there ...

As well, we can now convert the image (psd) to PDF.

The short answer is that that patch appears to resolve the issue, identify +ping FILENAME.psd worked. Here's the output after patching psd.c: identify +ping FILENAME.psd 0: 0,0 135,181 135,181 1: 0,0 0,0 0,0 2: 0,0 0,0 0,0 3: -10,-20 140,255 150,275 4: -10,-20 140,255 150,275 5: 0,0 0,0 0,0 6: -21 ...

I've posted the debug log to: http://www.darkart.com/ImageMagick_identify_debugAll.20101008.1806.txt The particular things I noticed were at: lines 393 and 396 where there's an entry for "Area: 2.88622TB/2.88622TB/4.295GB" (that 4.295GB was present above too) and for "Disk: 2.88622TB/2.88622TB/18 ...

Unfortunately 6.6.4-10 beta (from a couple of days ago) still fails on our particular image. I have debug output that I can send to someone, it appears that identify is trying to allocate ~2.88 TB on disk which then fails and then identify crashes. Please let me know the best way to get the debug ...

I confirmed that 6.6.4-10 beta works to run 'identify +ping ubuntu-imagemagick-hang.psd'. I'll confirm against our data as soon as I can.

Bingo. The PSD mentioned in: http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=16721&p=61626&hilit=psd#p61626 also causes this crash. The image is available from: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/597469 or directly at: https://bugs.launchpad.net/ubuntu/+source ...

Converting just the composite does work, however we need to have the layers as well. Adding the '-limit area 0' still results in the same crash. Trying to get other layers (convert image.psd[1] image.pdf) crashes as well - all crashes have the same stack trace, just different threads. Unfortunately ...

We're seeing an issue with ImageMagick-6.6.4-9 converting PSD files to PDF - at least one file is consuming a very large amount of memory (20+G of private mem). Trying to run 'identify +ping IMAGEFILE.psd' results in a crash (see below for crashed thread stack). We were able to convert this image ...

FYI-
This problem appears to be fixed in 6.6.2-9. Data that exhibited the failure now works properly. Thanks much!

We may be able to help test, unknown if we can help with coding due to limited resources but pointers to things to check on would help in that area. I forgot to mention that these files have been fine with Mac OS X 10.5.8 and 32bit 'convert', have not tried building ImageMagick 32bit on 10.6.3 to ...

'convert' fails to convert some PSD files to PDF on Mac OS X 10.6.3 as it tries to allocate a very very large chunk of memory (18+ quintillion bytes, but not all bits in a 64bit integer are turned on). It reports that the error is: @ error/pdf.c/WritePDFImage/1557 This is ImageMagick 6.6.2-0 built ...

It appears this is fixed in 6.3.9-5, thanks much!

I have a similar problem, my source is a gif w/ an alpha channel. The created PDF has the SMask referring to object 15 while the SMask data is in object 16. Adobe Reader (v 8.1.2, Mac OS X 10.5.2, x86) gives and error 14 if the SMask refers to object 15. If I edit the PDF to set the SMask to refer ...