We have an online photo editting tool.
Occaisonally users manage to upload huge files to manipulate without going
through the nice resize image sensibly before upload tool, and without the
upload timing out on them(!). This can cause resource spikes with the memory
used in ImageMagick leaping to 800MB plus per user resizing large images.
Experiments setting map-limit memory-limit and disk-limit, suggest the first
two work as expected, but that disk-limit seems to be ignored. In that I
thought this would limit the maximum size of the files created on disk, but I
see files many times larger than the limits I choose created
as "/tmp/magick*"
$img->SetAttribute('memory-limit' => ...
$img->SetAttribute('map-limit' => ...
$img->SetAttribute('disk-limit' => ...
Not a huge issue, since it will all time-out and clean-up if the users gets
too ambitious, but have I misunderstood what disk-limit does, got the name
wrong, or is there some subtlety to it I've missed?
This is all tested on Debian Etch
perlmagick 6.2.4.5.dfsg1-0.14
_______________________________________________
Magick-users mailing list
[email protected]
http://studio.imagemagick.org/mailman/listinfo/magick-users
