This is not an error with Drupal, Wordpress or any other CMS. This is a misconfiguration of the server. You need to set your configuration files for things like PHP, MySQL and Apache. Setting an unlimited memory amount (as you are doing here) is a dangerous practice. Drupal currently handles it the proper way.
I responded yesterday with how to increase PHP's memory limit. The *Fatal error*: Allowed memory size of 134217728 bytes being identical is exactly how it's supposed to be. That means PHP's INI file is set to a memory limit of 128mb (134217728 bytes = 128mb). A lot of Drupal installations can run on that, but you can also keep adding modules, complex views, panels and a bunch of other stuff that will quickly exhaust that amount of memory. That's why it is up to each site to adjust it to whatever they need.
Jamie Holly http://www.intoxination.net http://www.hollyit.net
On 2/7/2013 1:57 AM, Roger wrote:
I believe the problem is in the way Drupal allocates memory for php, or vice versa -but this is only a theory.
I see that the problem has existed for years and is prevalent also in Wordpress. The error message: *Fatal error*: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16142054 bytes) in */var/www/html/mysite/includes/database/database.inc* on line *2139*....Is quite curious.
It varies in file name and amount tried to allocate but remarkably the the error message: *Fatal error*: Allowed memory size of 134217728 bytes exhausted is identical in all cases, is it hard coded somewhere?
There is a workaround. Right at the very end of settings.php include one line: ini_set('memory_limit','-1'); This overrides PHP settings for the particular Drupal install.
Maybe Drupal aficionados and coders could attend to this before Drupal gets to Ver 8