Page 1 of 1
Posted: 2006-09-01T07:30:57-07:00
by magick
25GB seems a bit excessive. You could set the MAGICK_DEBUG environment variable to 'cache' to see what's going on. If you have the time, try ImageMagick 6.2.9. Consider using the Q8 version of ImageMagick rather than the default Q16 version. Make sure you are destroying an image after you are done with it so it does not persist and waste resources. Also take a look at
http://www.imagemagick.org/script/architecture.php.
Posted: 2006-09-03T10:03:55-07:00
by magick
We would need to reproduce the problem before we could speculate what the problem may be. If you can illustrate the problem with say 50 lines of code or less, post it here and we will try to reproduce the problem and either provide a patch or explain why large temporaries are being created.
Posted: 2006-09-03T17:59:51-07:00
by dognose
I'll just add that I'm having the same problem as well.
my system is on a machine with a lot of users uploading images, some of which are clearly invalid and it's been filling the disk space. Since the convert crashes or is killed when processing some extra large images, I guess the temorary files are sticking around.
.. just noticed I'm using 6.2.8.. I'll try 6.2.9 and see how it goes.
edit:
Uhg.. can't upgrade to 6.2.9
freetype2-devel is needed by ImageMagick-6.2.9-3.x86_64
Anyone know where to get or build a freetype2 rpm?
Posted: 2006-09-03T19:36:36-07:00
by magick
You can set the disk cache resource limit to 1GB and this will prevent users from creating huge images. See
http://magick.imagemagick.org/script/ar ... .php#cache for a discussion.
Posted: 2006-09-04T11:27:27-07:00
by dognose
Is there a way to set the disk cache resource limit globally?
I don't want to set it in the ENV or the command line.
Posted: 2006-09-04T12:18:14-07:00
by magick
Use MagickLib::SetMagickResourceLimit() to set the disk resource limit programatically.