Good Day,

I noticed that this new version needs more memory.

ImageCache PHP Memory Limit 64M
It is highly recommended that you set you PHP memory_limit to 96M to use imagecache. A 1600x1200 images consumes ~45M of memory when decompressed and there are instances where ImageCache is operating on two decompressed images at once.

What if it is not possible to increase the memory limit to 96M? Is it still recommended to use this version?

Thank you,

Mark

Comments

dopry’s picture

dopry commented
Status: Active » Postponed (maintainer needs more info)

Why couldn't you increase the php memory limit? If you can't you have an inappropriate hosting arrangement for drupal.

mrgoltra’s picture

mrgoltra commented

i have created my own php.ini and when I change the memory limit to 96M it still gives me that notification. I only notice this on 5.7 and not on 6.2. On version 6.2 it reflects the changes. I have run cron and update but its still there.

I am not sure if the status report is just a fluke. I also seem to be having a few issues using imagecache. some of the images are not being scaled down. I am still testing...

drewish’s picture

drewish commented

might be a hard limit on a virtual server... i've run into that and basically we had to either pay for an upgraded server or just start using imagemagick.

dopry’s picture

dopry commented

@mrgoitra: does php_info() say that it is using your custom php.ini? It might not be reading it. You can also use imagemagick as an alternative if you can't meet the GD memory requirements.

mrgoltra’s picture

mrgoltra commented

i have 5 sites on this server 3 are 5.7 and one is running 6.2. No problem with that one. it shows that memory limit is set to 96M it is only the 5.7 sites that are reporting this. Time to contact support.. can't even get phpinfo

dopry’s picture

dopry commented

oh hrm... but I should probably set that warning to only get thrown if imageapi_gd is in use.... hrm.... maybe I should move this requirement to imageapi_gd

ChristieLuv’s picture

ChristieLuv commented

With a lot of servers you can change your memory limit in htaccess. If image cache is saying this, put this in your htaccess file:

php_value memory_limit 96M

The .htaccess file should be in your drupal directory and your webhost must have "AllowOverride On" in their httpd config.

You can check if it worked by making a phpinfo.php phpinfo(); file into your drupal directory to check if the value of memory_limit changes. The "master" value should still be the same MB afterwards but the "local" value (left column) should have changed to 96M.

For me in 5.7 it is still saying its the old setting while PHP info says its changed. I'm not sure if this will cause any problems, probably not because it is changed in any case whether it says it or not and probably is just reading what the master setting says. While at the same time your settings are changed.

I'll be sure to let you all know if I run into any.

dortez’s picture

dortez commented
Status: Postponed (maintainer needs more info) » Fixed

@ChristieLuv,

Thanks that worked!

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Fixed » Active

I haven't used a shared host yet that allows more than 64MB. I can accept that I have a limit on the size of images I can handle. What I don't like is the permanent warning on my admin pages. Please allow some way to turn that message off.

rc2020’s picture

rc2020 commented

Hey,

I am also getting this error. I believe that my php memory settings are currently set to 96M in my php.ini file in my server directory. However, I am still getting this warning. When I tried to put that in my .htaccess file, my server would crash. Is there another way I could set the memory limit to be 96m?

Thanks.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

http://drupal.org/node/207036

rc2020’s picture

rc2020 commented

Thanks I looked and actually my php ini values were at 64. Thanks!

drewish’s picture

drewish commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.