Legacy ImageMagick Discussions Archive

I just found about IMAGEMAGICK_OPENCL_CACHE_DIR variable that can be used to fix this problem. However, it would still be nice to have some kind of automated fallback to /tmp in case the cache directory is not writable.

When ImageMagick is executed under a limited user account (eg. the common "nobody" user) the OpenCL tests are executed every time because the results can't be written into ~/.config/ImageMagick/since the user doesn't have a writable home directory. As a result, the execution always takes very long ...

It has been fixed in ImageMagick 6.8.7-10. Thank you!

I just found out that it happens only when "Intel SDK for OpenCL" is installed. I thought that it may be caused by the fact that in Intel OpenCL supports OpenCL 1.2 while nVidia supports only 1.1, but uninstalling nVidia OpenCL drivers doesn't change anything. It looks like a bug in the Intel's ...

It still crashes with 6.8.7-10. Here's an updated backtrace: #0 0x0000000000000000 in ?? () #1 0x00007ffff7a3286e in initDSProfile (version=0x7ffff7b3afa0 "ImageMagick Device Selection v0.9", p=<synthetic pointer>) at magick/opencl.c:1388 #2 autoSelectDevice (clEnv=0x6299d0, exception=0x604f10) at ...

Can you attach the file $HOME/.magick/ImagemagickOpenCLDeviceProfile here? I don't have such file in my home. Backtrace from 6.8.7-9: #0 0x0000000000000000 in ?? () #1 0x00007ffff7a3286a in initDSProfile (version=0x7ffff7b3b020 "ImageMagick Device Selection v0.9", p=<synthetic pointer>) at magick ...

Thank you for the reply, using --disable-opencl does fix the crash. I have already tested ImageMagick 6.8.7-9 and the crash is still present.

Running an application from imagemagick (tested with convert and mogrify) with -resize parameter causes a crash with the following output: Aborted (core dumped) The problem first occurred between imagemagick-6.8.7.2 and imagemagick-6.8.7.4. When I run "convert -resize 128x128 test.png a.png" I was ...