By waldmanm on

I got the following error when running update.php after upgrading from 6.14 to 6.15:
"Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 52467 bytes) in /home8/geminsig/public_html/includes/cache.inc on line 105"

I'm not sure if it's related specifically to the new release, because I've seen similar messages (memory exhausted) before when doing various administration activities on my site. However, I've tried upgrading to 6.15 twice (after restoring back to 6.14), with the same results, so I cannot upgrade at this point.

Any help would be appreciated. Any idea on why so much memory is used in the first place, and whether this problem is related to my hosting service limitations (using Blue Host) or to 6.15?

Details:
- I copied the new 6.15 files, then ran update.php. It recognized the version I'm coming from and started running the update itself but then I got this message above.
- Once I copied the 6.14 files back and restored my db from a backup, the site is back to functioning.
- There's very little data in the DB (I'm just getting started). The following modules are enabled:
advanced_help
backup_migrate
captcha
cck
content_taxonomy
date
dirtyforms
front
jquery_ui
noderelationships
onbeforeunload
page_title
recaptcha
taxonomy_manager
token
views
wysiwyg

Many thanks,
Micah

⋅ Categories: Drupal 6.x

Comments

gpk’s picture

gpk commented

>I've seen similar messages (memory exhausted) before when doing various administration activities on my site.
Try disabling as many contrib modules as possible before doing the upgrade.

Then either speak to your host about increasing your PHP RAM allocation, or find out which module is using so much RAM. I have a site that uses many more contrib modules than that and most page requests (including admin pages) require less than 15MB, as measured by devel.module.

gpk
----
www.alexoria.co.uk

waldmanm’s picture

waldmanm commented

Thanks, gpk.

Unfortunately, I get similar errors when trying to enable the devel module, so I cannot move forward ... I'll try to start from a fresh core install with devel and then add my modules gradually to try to identify the culprit.

Micah

gpk’s picture

gpk commented

>similar errors when trying to enable the devel module
You probably need to disable as many other modules as possible first!!!

gpk
----
www.alexoria.co.uk

waldmanm’s picture

waldmanm commented

I finally got around to confirm that increasing the PHP memory limit indeed resolved all problems, and the upgrade to 6.15 went smoothly. So this had nothing to do with the new 6.15 release.

Here is the link to the BlueHost knowledge-base article that explains how to set the memory limit: http://helpdesk.bluehost.com/index.php/kb/article/000110 . Its title refers to upload_max_filesize but it deals with memory_limit too. I changed my limit to 96MB and everything is working fine now. Note that the Apache server does not need to be restarted - you just need to follow the instructions. Once you create php.ini.default don't forget to rename it to php.ini (yes, I was working on this late at night ... :).

Thanks to everyone for the help and tips.

Micah

Kode-1’s picture

Kode-1 commented

Just call Blue Host and ask them to increase your memory size. They shouldn't have a problem doing it.

chrisdfeld’s picture

chrisdfeld commented

I had the same problem with a local Drupal install that I've just upgraded from 6.14 to 6.15. update.php completed fine, then when trying to return to the home page or admin area I got the out-of-memory error.

This copy of Drupal is running on an XAMPP install under Windows. PHP's memory limit was set at 32M in php.ini. The site has a whole bunch of modules installed but memory has never been an issue before, although this is the first Drupal upgrade I've done on this particular site.

After increasing the PHP memory limit to 64M I could load the site once more. I then turned off maintenance mode and bumped the memory back down to 32M and things are again working fine at the lower memory limit. Very strange. It's my feeling that Drupal should not be consuming this much memory; many web hosts don't even allow 32M, let alone 64M. I can set my own limit with my local Apache but others will be at the mercy of their web host. For servers with 32M or lower PHP memory limits, it might be advisable to go to the trouble of disabling custom and contributed modules before performing the 6.15 upgrade.

gpk’s picture

gpk commented

>then when trying to return to the home page or admin area I got the out-of-memory error... It's my feeling that Drupal should not be consuming this much memory
After running the update process various caches have to be rebuilt, this is probably what is causing the problem.

32M is recommended for 6.x sites with not too many contrib modules but as this page says http://drupal.org/node/207036 you may well need more than that for sites with "a whole bunch of modules installed". I'd suggest leaving it at 64M - it can't do much harm.

gpk
----
www.alexoria.co.uk

gpk’s picture

gpk commented

>then when trying to return to the home page or admin area I got the out-of-memory error... It's my feeling that Drupal should not be consuming this much memory
After running the update process various caches have to be rebuilt, this is probably what is causing the problem.

32M is recommended for 6.x sites with not too many contrib modules but as this page says http://drupal.org/node/207036 you may well need more than that for sites with "a whole bunch of modules installed". I'd suggest leaving it at 64M - it can't do much harm.

gpk
----
www.alexoria.co.uk

crabsoul’s picture

crabsoul commented

Hi,

you can increase memory limit from setting.php file as well. add this line in setting.php file:
ini_set('memory_limit', '100M');

Hope it will help.

Regards
Rashmi