Allowed memory exhausted

Posted by petiar on January 7, 2009 at 10:09am

Hi everybody,

I have got strange problem - when trying to access Modules admin page I am getting the well-known
Fatal error: Allowed memory size of 50331648 bytes exhausted (tried to allocate 280986 bytes) in /data/f/o/folk.sk/web/includes/database.mysql.inc on line 301.

This has started to happening after I installed some module - cant remember which one. So I have uninstalled it (setting value status in system mysql table for this particular module to 0). But this error is still appearing. So I performed total cleaning through all my modules - I deactivated/uninstalled/removed all unused modules. And I am still getting that error. So the actuall status is that I have even less modules installed but I am getting that ugly message. My allowed memory is 48k. Do not advise do increase it - it is not possible for me. It must work even with this amount of memory, because it did work before.

Thanks for your help.
Petiar.

Comments

allowed memory 48k ?? Normal

Posted by alakesh on January 7, 2009 at 10:22am

allowed memory 48k ??

Normal drupal 6 installation required 16MB memory.
Go to php.ini and set memory limit to something big like 32M or 64M.

memory_limit = 32M ;

You will also need to restart Apache for that change to take affect.

Sorry, 48M, of course.

Posted by petiar on January 7, 2009 at 11:26am

Sorry, 48M, of course. ;-)

--
Petiar
The biggest slovak folk music magazine proudly uses Drupal
http://folk.sk

--
Petiar
http://petiar.sk

Try measuring usage

Posted by peterx on January 7, 2009 at 10:48am

Try measuring usage:
http://2bits.com/articles/measuring-memory-consumption-by-drupal-bootstr...

Drupal 6 is more efficient than 5 but not all modules improved. APC or equivalent will reduce memory usage by removing script compilation. Things hang around in sessions and other places when you jump around pages. Does the error occur after closing the browser, opening the browser, logging in and going straight to the modules admin page without visiting any other pages?

Did you switch any administrator options on or off, such as caching? Did you change themes?

The modules list loads every module, including disabled and uninstalled modules, to find out what they need. Delete the modules from disk. Delete the relevant module row from the system table.

petermoulding.com/web_architect

Thanks for your reply. I

Posted by petiar on January 7, 2009 at 11:31am

Thanks for your reply.

I have tried to close the browser and after reopening it I was able to access admin/build/modules page succesfully. But when I have done reload this error appeared again. It looks like something is hanging out there - any idea what it could be?

I did not change any admin options, nor theme. When I am removing module I always delete it from disk. I am going to try to delete the table row as well.

--
Petiar
The biggest slovak folk music magazine proudly uses Drupal
http://folk.sk

--
Petiar
http://petiar.sk

So I have clean-up both disk

Posted by petiar on January 8, 2009 at 10:49pm

So I have clean-up both disk and database - got rid of all non-used modules. Now I have like half of the amount I used to have and I am still getting that error message. Any other ideas?

--
Petiar
The biggest slovak folk music magazine proudly uses Drupal
http://folk.sk

--
Petiar
http://petiar.sk