Fatal error on allowed memory size, regardless of how high memory_limit set to in php.ini. Needed to delete modules. What gives?

I have the same issue, with a little twist. It's giving me a specific location. The error is in the DATE Module. But i've been using the module just fine.

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /home/tran9775/public_html/sites/all/modules/date/includes/date_api_filter_handler.inc on line 397

Here is the code from line 396 (Included the comments)
/**
* Custom implementation of query() so we can get the
* AND and OR methods in the right places.
*/
function query() {
$this->ensure_my_table();
$this->get_query_fields();
if (!empty($this->query_fields)) {
foreach ((array) $this->query_fields as $query_field) {
$field = $query_field['field'];
$sql = '';
$sql_parts = array();
switch ($this->operator) {
case 'between':
$sql_parts[] = $this->date_filter('min', $query_field, '>=');
$sql_parts[] = $this->date_filter('max', $query_field, '<=');
$sql = implode(' AND ', array_filter($sql_parts));
break;
case 'not between':
$sql_parts[] = $this->date_filter('min', $query_field, '<');
$sql_parts[] = $this->date_filter('max', $query_field, '>');
$sql = implode(' OR ', array_filter($sql_parts));
break;
default:
$sql = $this->date_filter('value', $query_field, $this->operator);
break;
}
if (!empty($sql)) {
// Use set_where_group() with the selected date_method
// of 'AND' or 'OR' to combine the field WHERE clauses.
$this->query->set_where_group($this->options['date_method'], 'date');
$this->query->add_where('date', $sql);
}
}
}
}

I tried removing that section of code. I just started using Drupal a week ago, so I'm not so familiar with the code.

Joseph

If you just delete the folder, without disabling the module first, your drupal site itself might go down, spitting plenty of error messages.

You need to first increase your memory limit higher in php.ini file in the root folder (public_html) so that you are able to access your modules page.

Even for a production site with plenty of module including Views module (which is the known memory hog) 128M php memory should be good enough.

For what it's worth, here's how I solved my problem. Again, I use Bluehost.com for my host, so your mileage may vary...

First I changed my memory_limit to 128M in the php.ini file in my root directory.

That didn't solve the problem so I called Bluehost.

They had me go into the Control Panel (at Bluehost.com) and select PHP Config. Then, I selected the option:

PHP5 (Single php.ini)
Same as PHP5, but all subdirectories will use ~/public_html/php.ini

That did the trick! I don't know if the tech from Bluehost made any changes on his end behind the scenes; I don't think he did though.

Hope that helps somebody!

This is likely an induced hard error - in your case likely you server is set to 35 meg - no matter what you select in the PHP.INI See reply above to the user "cfab"

Bob Burns
Certified UNIX Engineer

If the error message still says the same amount of allowed memory size, then you have not actually raised it. Double check via the drupal status report page or use phpinfo to confirm you've actually made the adjustment.

The number of 'pages' in a drupal site has very little, if anything, to do with the amount of resources it consumes. I could have a one page site-- depending on the number and type of modules I'm using and the amount of concurrent user traffic it could still overwhelm the usually minuscule restrictions of a shared hosting environment.

And what I said above applies in your case as well, if the error message consistently comes back with the same initial allowed size, you may not have actually made the change. I can't speak to hostgator or what cfab said above (http://drupal.org/node/466254#comment-2037880), but every time I've verified that memory outside of drupal with phpinfo, it's been correct.

And also, keep in mind, no matter what you set the memory to in software, you'll always be constrained by the physical memory of the box or vm.

I switched to using simplemenu (http://drupal.org/project/simplemenu) which has a smaller memory footprint. The admin menu also executes an sql query on every page load to look up the number of logged in users, this is really not necessary.

BTW, the devel module has a setting to display each page's memory usage which can be really helpful figuring out which modules and pages are consuming a lot of memory.