Legacy ImageMagick Discussions Archive

That patch looked promising, at least for the other guy's backtrace. For me it doesn't seem to make a difference, and he reports: Yes, it looked promising, but it didn't help. Same backtrace: #0 0x00007f7ff740656d in sem_wait (sem=0x7f7ff31bbf00) at /archive/foreign/src/lib/libpthread/sem.c:260 #1 ...

sorry to keep replying to myself... it is news as it happens ;-) I've updated my ImageMagick to ImageMagick-6.8.9.0 and alas, it doesn't help. The other person reported they were at that version already, I just hear. They also report: On Sat, Apr 26, 2014 at 10:32:30PM +0200, Rhialto wrote: > I just ...

Yes, I notice no problem when configuring with --disable-openmp. So that seems to indicate I'm at least looking in the right area. Next I'll try to see how doable it is to update ImageMagick. I was going to try that on a laptop which is a bit expendable than the machine where I discovered the ...

It happens with version ImageMagick-6.8.8.5. It's not so easy to update it due to the things that use it. But it should be doable to replace in-place it with a version configured with --disable-openmp. I'll try that first, to confirm that that avoids the problem.

Hi there, a fellow NetBSD user and I independently came across two crashes in Calibre, which seemed to have in common that they both occurred due to calls from the libMagickCore-6.Q16.so.2 library. (The version is ImageMagick-6.8.8.5) The common pattern is that something from ImageMagic calls a ...