[Magick-bugs] huge magick-XX files in wrong path (2)

[c.baegert-listes at lixium.fr]

Hi,

This is the following of the problem I mentioned on May 20th.

I have a big problem with ImageMagick, it seems that sometimes it creates huge 
magick-XX... files. I suppose it's a crash on particular pictures. Well, 
that's annoying, but it's not my worst problem. The worst problem is that 
these files are created in the current path on a NFS mount, and this 
collapses my NFS server, and then all my other webservers !

This happens although I specified a dedicated local temporary path to save 
them (to crash only one server when ImageMagick crashes) :

/usr/local/bin/convert -set 
registry:temporary-path /tmp /home/xxxx/yyyyy/sessions/73beaad5d67a4f5365fa9777e2600627/od3e02f1d93928948a018818d7d35f1e8_1.pdf -resize 
470x470 -bordercolor #000000 -border 1 -matte ( +clone -background 
black -shadow 50x4+5+5 ) +swap -background 
#FFFFFF -flatten /home/xxxxxxx/yyyyyy/sessions/73beaad5d67a4f5365fa9777e2600627/pr_470_od3e02f1d93928948a018818d7d35f1e8_1_FFFFFF.jpeg

/usr/local/bin/convert -set registry:temporary-path /tmp -limit memory 
32mb -limit map 
64mb /home/xxx/yyy/sessions/ac81808fb7a5048fcab491c93cfdbb1d/f7ff73ea6e7818d1ed8a67e5977090aa.jpeg -resize 
300x300 -colorspace 
RGB /home/xxx/yyy/sessions/ac81808fb7a5048fcab491c93cfdbb1d/p_300_f7ff73ea6e7818d1ed8a67e5977090aa.jpeg

After the answer I had on this list on May 20th, I added "TMPDIR=/tmp " in 
front of the command line, but I still have the problem. So I really think 
now there's a bug in Imagemagick 6.3.8 about temporary directory.

I saw there's now a 6.4 version, but I already upgraded from 6.2.8 to 6.3.4 to 
see if this bug was fixed without success, and the customer needs extensive 
validation at each upgrade, so it will be difficult for me to ask to him once 
more to upgrade "only to see if the bug has been fixed". It's difficult as 
well to test it without using it in production since it's a random bug I 
never managed to reproduce.

Does someone know if this bug is fixed in the new 6.4.x versions ?

Regards,
-- 
Christophe