Reduce memory usage? about imagine HOT 7 CLOSED

Here's my code:

$imagine = new \Imagine\Gd\Imagine();
$image = $imagine->open($dir_uploads2.DS.$fn_shot);


//figure out size of cropped image
$image_box = $image->getSize();
$width = $image_box->getWidth()-28;     //border x 2 = 28px
$height = $image_box->getHeight();
$cropped_size = new Imagine\Image\Box($width, $height);



//add black border
$border_width = 50;
$new_box = $image->getSize()->increase($border_width*2);
$color = new Imagine\Image\Color('000');    //black
$image2 = $imagine->create($new_box,  $color);
$border_startpoint = new Imagine\Image\Point($border_width,$border_width);
$image2->paste($image, $border_startpoint);

//output new image          
$image2->save($dir_uploads2.DS.$fn_shot);

from imagine.

What kind of canvas dimensions are you working with? Imagine works with true color image resources, and those are prone to taking up quite a bit of memory (at least 3 bytes per pixel). I've run into similar issues of high memory consumption while resizing uploaded images. Despite limiting uploads to a few MB, a highly compressed JPG could expand considerably in memory when opened as an image resource.

from imagine.

Alternatively I suggest using Imagick/Gmagick drivers as those won't keep image in memory

from imagine.

My images are 2000 x 1500 JPGs.

And being a shared server I can't install Imagick/Gmagick :(

from imagine.

You run out of memory processing just one image or are you using it for mass processing?

from imagine.

Multiple images but one at a time in a loop, so the $image and $image2 vars are being replaced every iteration.

I was able to workaround this issue by adding an unset($image) before the ->save call, I guess the ->save creates another copy of the image and 3 copies of the image was too much for 64Mb:

unset($image)
$image2->save($dir_uploads2.DS.$fn_shot);

Thanks for the help guys.

from imagine.

unset($image) isn't working for me, I have to use ini_set('memory_limit', '1024M'); to make it work. But that has a limitation in itself, if inside loop there are more than 50 images each 3-7MB in size, it may break after allocating '1024M' but if I use ini_set('memory_limit', '-1'); that is unlimited memory. It will never break but this is not the correct way of solving this issue because this unlimited memory allocation can cause other damage to the server as well. So what would be the best way to resolve it.

from imagine.