identify -verbose seg faults on PSD files

Post any defects you find in the released or beta versions of the ImageMagick software here. Include the ImageMagick version, OS, and any command-line required to reproduce the problem. Got a patch for a bug? Post it here.
Post Reply
jeffATwork
Posts: 30
Joined: 2009-01-02T14:14:45-07:00
Location: Minneapolis, MN
Contact:

identify -verbose seg faults on PSD files

Post by jeffATwork »

IM 6.5.7-8.

Tried on 7 (~100MB) files. Only one succeeded.

I can put a sample file up on Dropbox or ??

Thanks!
snibgo
Posts: 12159
Joined: 2010-01-23T23:01:33-07:00
Authentication code: 1151
Location: England, UK

Re: identify -verbose seg faults on PSD files

Post by snibgo »

If you put up a sample, someone can test on more recent versions of IM.
snibgo's IM pages: im.snibgo.com
User avatar
dlemstra
Posts: 1570
Joined: 2013-05-04T15:28:54-07:00
Authentication code: 6789
Contact:

Re: identify -verbose seg faults on PSD files

Post by dlemstra »

With ImageMagick 6.8.6-8 on Windows 7 I can run identify -verbose house_01.psd without any problems.
.NET + ImageMagick = Magick.NET https://github.com/dlemstra/Magick.NET, @MagickNET, Donate
snibgo
Posts: 12159
Joined: 2010-01-23T23:01:33-07:00
Authentication code: 1151
Location: England, UK

Re: identify -verbose seg faults on PSD files

Post by snibgo »

Code: Select all

convert house_01.psd h.png
It converts fine for me, IM v6.8.6-0 on Windows 7, on a 4 GB laptop, creating 40 files.
snibgo's IM pages: im.snibgo.com
jeffATwork
Posts: 30
Joined: 2009-01-02T14:14:45-07:00
Location: Minneapolis, MN
Contact:

Re: identify -verbose seg faults on PSD files

Post by jeffATwork »

Thanks for your efforts.

I'm running Linux 2.6.32-40-server #87-Ubuntu SMP Tue Mar 6 02:10:02 UTC 2012 x86_64 GNU/Linux
Ubuntu 10.04.4 LTS

I'll check with my sysadmin, but any other suggestions?
Bonzo
Posts: 2971
Joined: 2006-05-20T08:08:19-07:00
Location: Cambridge, England

Re: identify -verbose seg faults on PSD files

Post by Bonzo »

If you notice the two successes were on a lot newer version of IM than yours - there could be a problem with your version?
jeffATwork
Posts: 30
Joined: 2009-01-02T14:14:45-07:00
Location: Minneapolis, MN
Contact:

Re: identify -verbose seg faults on PSD files

Post by jeffATwork »

Yes, the successes were on newer versions. Unfortunately, Ubuntu is mired in the past.

I tried running one of the failing identify commands under valgrind. At the point where the seg fault occurs, I get the following:

==12994== Warning: silly arg (-21474812544) to malloc()
==12994== Invalid read of size 1
==12994== at 0x4F4B79B: ??? (in /usr/lib/libMagickCore.so.2.0.1)
==12994== by 0x4F4C0F4: DestroyQuantumInfo (in /usr/lib/libMagickCore.so.2.0.1)
==12994== by 0x4F4C1D7: AcquireQuantumInfo (in /usr/lib/libMagickCore.so.2.0.
1)
==12994== by 0x4F71603: SignatureImage (in /usr/lib/libMagickCore.so.2.0.1)
==12994== by 0x4F157CE: IdentifyImage (in /usr/lib/libMagickCore.so.2.0.1)
==12994== by 0x52E6BBB: IdentifyImageCommand (in /usr/lib/libMagickWand.so.2.0.1)
==12994== by 0x533C892: MagickCommandGenesis (in /usr/lib/libMagickWand.so.2.0.1)
==12994== by 0x400A8F: ??? (in /usr/bin/identify)
==12994== by 0x5A2EC4C: (below main) (libc-start.c:226)
==12994== Address 0xfffffffb00005d7f is not stack'd, malloc'd or (recently) free'd
==12994==
==12994==
==12994== Process terminating with default action of signal 11 (SIGSEGV)
==12994== Access not within mapped region at address 0xFFFFFFFB00005D7F
==12994== at 0x4F4B79B: ??? (in /usr/lib/libMagickCore.so.2.0.1)
==12994== by 0x4F4C0F4: DestroyQuantumInfo (in /usr/lib/libMagickCore.so.2.0.1)
==12994== by 0x4F4C1D7: AcquireQuantumInfo (in /usr/lib/libMagickCore.so.2.0.1)
==12994== by 0x4F71603: SignatureImage (in /usr/lib/libMagickCore.so.2.0.1)
==12994== by 0x4F157CE: IdentifyImage (in /usr/lib/libMagickCore.so.2.0.1)
==12994== by 0x52E6BBB: IdentifyImageCommand (in /usr/lib/libMagickWand.so.2.0.1)
==12994== by 0x533C892: MagickCommandGenesis (in /usr/lib/libMagickWand.so.2.0.1)
==12994== by 0x400A8F: ??? (in /usr/bin/identify)
==12994== by 0x5A2EC4C: (below main) (libc-start.c:226)
==12994== If you believe this happened as a result of a stack
==12994== overflow in your program's main thread (unlikely but
==12994== possible), you can try to increase the size of the
==12994== main thread stack using the --main-stacksize= flag.
==12994== The main thread stack size used in this run was 8388608.
==12994==
==12994== HEAP SUMMARY:
==12994== in use at exit: 496,674,299 bytes in 7,411 blocks
==12994== total heap usage: 19,841 allocs, 12,430 frees, 1,318,342,413 bytes allocated
==12994==
==12994== LEAK SUMMARY:
==12994== definitely lost: 0 bytes in 0 blocks
==12994== indirectly lost: 0 bytes in 0 blocks
==12994== possibly lost: 6,992 bytes in 23 blocks
==12994== still reachable: 496,667,307 bytes in 7,388 blocks
==12994== suppressed: 0 bytes in 0 blocks
==12994== Rerun with --leak-check=full to see details of leaked memory
==12994==
==12994== For counts of detected and suppressed errors, rerun with: -v
==12994== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4)
Killed

I don't know whether there is a problem with our installation of ImageMagick or whether this is a bug in 6.5.7-8.

Suggestions?
snibgo
Posts: 12159
Joined: 2010-01-23T23:01:33-07:00
Authentication code: 1151
Location: England, UK

Re: identify -verbose seg faults on PSD files

Post by snibgo »

The oldest version I have is 6.5.8-8, on Windows 7. It successfully creates the 40 files.
snibgo's IM pages: im.snibgo.com
jeffATwork
Posts: 30
Joined: 2009-01-02T14:14:45-07:00
Location: Minneapolis, MN
Contact:

Re: identify -verbose seg faults on PSD files

Post by jeffATwork »

thanks snibgo. Aside from the OS, that's pretty close.
User avatar
fmw42
Posts: 25562
Joined: 2007-07-02T17:14:51-07:00
Authentication code: 1152
Location: Sunnyvale, California, USA

Re: identify -verbose seg faults on PSD files

Post by fmw42 »

On IM 6.8.6.8 Q16 Mac OSX I get:

Code: Select all

identify house_01.psd
house_01.psd[0] PSD 3240x2376 3240x2376+0+0 8-bit sRGB 108.8MB 2.170u 0:02.190
house_01.psd[1] PSD 2808x2376 2808x2376+216+0 8-bit sRGB 108.8MB 2.150u 0:02.200
house_01.psd[2] PSD 4787x2426 4787x2426-882-8 8-bit sRGB 108.8MB 2.140u 0:02.179
house_01.psd[3] PSD 1909x1191 1909x1191+673+554 8-bit sRGB 108.8MB 2.080u 0:02.119
house_01.psd[4] PSD 1909x1191 1909x1191+672+553 8-bit sRGB 108.8MB 2.070u 0:02.109
house_01.psd[5] PSD 1909x1191 1909x1191+672+554 8-bit sRGB 108.8MB 2.060u 0:02.099
house_01.psd[6] PSD 1909x1191 1909x1191+671+553 8-bit sRGB 108.8MB 2.060u 0:02.099
house_01.psd[7] PSD 1909x1191 1909x1191+672+553 8-bit sRGB 108.8MB 2.050u 0:02.089
house_01.psd[8] PSD 1909x1191 1909x1191+672+554 8-bit sRGB 108.8MB 2.050u 0:02.089
house_01.psd[9] PSD 1909x1191 1909x1191+673+553 8-bit sRGB 108.8MB 2.040u 0:02.079
house_01.psd[10] PSD 1909x1192 1909x1192+673+552 8-bit sRGB 108.8MB 2.040u 0:02.079
house_01.psd[11] PSD 1909x1192 1909x1192+674+552 8-bit sRGB 108.8MB 2.030u 0:02.069
house_01.psd[12] PSD 1909x1192 1909x1192+672+552 8-bit sRGB 108.8MB 2.030u 0:02.069
house_01.psd[13] PSD 1909x1191 1909x1191+672+552 8-bit sRGB 108.8MB 2.020u 0:02.059
house_01.psd[14] PSD 1909x1191 1909x1191+675+552 8-bit sRGB 108.8MB 2.010u 0:02.049
house_01.psd[15] PSD 1494x462 1494x462+677+804 8-bit sRGB 108.8MB 1.970u 0:02.009
house_01.psd[16] PSD 1494x462 1494x462+677+804 8-bit sRGB 108.8MB 1.970u 0:02.009
house_01.psd[17] PSD 1494x462 1494x462+677+804 8-bit sRGB 108.8MB 1.970u 0:02.009
house_01.psd[18] PSD 1494x462 1494x462+677+804 8-bit sRGB 108.8MB 1.970u 0:02.009
house_01.psd[19] PSD 1494x462 1494x462+677+804 8-bit sRGB 108.8MB 1.970u 0:02.000
house_01.psd[20] PSD 919x621 919x621+1581+1102 8-bit sRGB 108.8MB 1.930u 0:01.970
house_01.psd[21] PSD 918x621 918x621+1581+1102 8-bit sRGB 108.8MB 1.930u 0:01.960
house_01.psd[22] PSD 918x621 918x621+1581+1102 8-bit sRGB 108.8MB 1.920u 0:01.960
house_01.psd[23] PSD 918x621 918x621+1581+1102 8-bit sRGB 108.8MB 1.920u 0:01.960
house_01.psd[24] PSD 927x619 927x619+1578+1105 8-bit sRGB 108.8MB 1.920u 0:01.960
house_01.psd[25] PSD 131x292 131x292+1375+1370 8-bit sRGB 108.8MB 1.880u 0:01.919
house_01.psd[26] PSD 131x292 131x292+1375+1370 8-bit sRGB 108.8MB 1.880u 0:01.919
house_01.psd[27] PSD 131x292 131x292+1375+1370 8-bit sRGB 108.8MB 1.880u 0:01.919
house_01.psd[28] PSD 131x293 131x293+1375+1370 8-bit sRGB 108.8MB 1.880u 0:01.919
house_01.psd[29] PSD 131x292 131x292+1375+1370 8-bit sRGB 108.8MB 1.880u 0:01.929
house_01.psd[30] PSD 131x292 131x292+1375+1370 8-bit sRGB 108.8MB 1.880u 0:01.929
house_01.psd[31] PSD 580x338 580x338+1837+1378 8-bit sRGB 108.8MB 1.850u 0:01.889
house_01.psd[32] PSD 580x338 580x338+1837+1378 8-bit sRGB 108.8MB 1.840u 0:01.889
house_01.psd[33] PSD 580x338 580x338+1837+1378 8-bit sRGB 108.8MB 1.840u 0:01.889
house_01.psd[34] PSD 580x338 580x338+1837+1378 8-bit sRGB 108.8MB 1.840u 0:01.889
house_01.psd[35] PSD 580x338 580x338+1837+1378 8-bit sRGB 108.8MB 1.840u 0:01.889
house_01.psd[36] PSD 580x338 580x338+1837+1378 8-bit sRGB 108.8MB 1.840u 0:01.889
house_01.psd[37] PSD 580x338 580x338+1837+1378 8-bit sRGB 108.8MB 1.840u 0:01.889
house_01.psd[38] PSD 2594x1641 2594x1641+112+275 8-bit sRGB 108.8MB 1.800u 0:01.849
house_01.psd[39] PSD 3240x2376 3240x2376+0+0 8-bit sRGB 108.8MB 1.790u 0:01.839
Post Reply