Drupal Association members fund grants that make connections all over the world.
I'm experiencing the white screen "Fatal error: Out of memory..." when trying to access:
1. .../admin/build/modules - 100% of the time
2. .../admin/build/views/list - intermittently
3. .../admin/reports/status - intermittently
4. .../admin - intermittently
e.g. - Fatal error: Out of memory (allocated 41156608) (tried to allocate 35 bytes) in /home/kilboa/public_html/includes/theme.inc on line 758
Prior to the error appearing I was running Drupal 6.10, MySQL database 5.1.30, PHP 5.2.8 with 128M php memory with no glitches on a shared server. One night after routine updates of a few modules the error started appearing. Even when I downgraded those modules it was too late. The damage was done.
HERE IS THE CATCH. The error appears after allocating no more than 41156608 bytes (~40M) in EVERY case, sometimes less. This is FAR below the memory limit, which my host - HostGator, has now upped to 512M in an effort to problem solve. They have overridden the set server limits in my case in an attempt to eliminate causes.
Also it doesn't just happen when accessing information from one specific module or module table. I've seen this error attached to:
1. .../sites/all/modules/simplenews/simplenews.admin.inc on line 1190
2. .../sites/all/modules/ubercart/uc_cart/uc_cart.pages.inc on line 190
3. .../includes/theme.inc on line 758
4. .../includes/database.mysql.inc on line 301
5. .../sites/all/modules/views/includes/admin.inc on line 2707
Since the error first occurred, I've upgraded to Drupal 6.11 (in hopes of overwriting any bugs) and I've completely removed some modules using Filezilla and taken many more offline directly through the database System table with no effect. I consistently rerun update.php throughout these changes. So the number of active modules is much less than before the error started to occur.
My host is trying everything but has commented, "...The issue is not that you're hitting the PHP limit, or even the apache limit. You don't appear to be. I honestly think you're hitting the MySQL server limit..."
Could this be a MySQL performance issue or server limit issue? I'm on a shared server. The MySQL database is on the same server as my site. Obviously trying to load the modules admin page is going to tax the database more than any other page I'd guess. But this certainly is not the typical, "you need to increase your php memory" issue that many face when this error occurs.
Did I get a corruption in the works somewhere? I do my Drupal core upgrades by the books exactly as written in the update.txt file, so I'd hoped a fresh install of 6.11 would have cleared it. Why is the error occurring at ~40M when there is so much more php and apache memory available?
Any insight would be appreciated. I'll try anything at this point. My site is like a car that is running fine. I just can't open the hood.