Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By bg_dcp on
I'm running 5.1 with at least 8 modules activated. I wound up deactivating the archive module in favor of an archive view I imported into my views module. So far, things seemed to be working fairly well, with the exception that I have some difficulty getting to my general admin page (admin/). I can get to any of the sub-pages with no problems. Here is the error I get when attempting to reach my admin/ page:
Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 256 bytes) in */htdocs/sites/all/modules/views/views_cache.inc on line 73
Then I uploaded and activated the image module. I configured it and uploaded an image. It worked with no apparent problems. Then I uploaded image_assist and, after activating it, could not load any pages without getting an error message. I deleted the folder, since I could no longer access the site. Still, now I cannot upload or import any images. Here is the error message I get trying to import an image:
Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 4096 bytes) in */htdocs/includes/image.inc on line 308
Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 213 bytes) in */htdocs/includes/database.inc on line 199
I am substituting the star for the domain portion of my url.
Question: Are these errors caused by my server not allowing enough memory usage for PHP/Drupal? Does Drupal have a problem with running numerous modules at once? I ask, because it seems the problems only occur as I add more modules. However, I could be barking up the wrong tree. If you know where I can find answers to these issues, just point me in the right direction - I don't mind doing a bit of reading.
Thanks in advance!
Comments
This seems to be a typical
This seems to be a typical php memory error. The default on your server is 12MB and there are three ways to increase it, depending on what your host allows. See:
http://drupal.org/node/29268
Try something like 24M
Solved -Thanks!
That was it! I really wasn't sure where to begin on this. Many thanks!
Memory...
I keep allocating more and more memory, but I still get the errors. It makes it all the way to pathauto now before running out of memory. We're up to 80MB now.
The funny thing is we don't have that many modules installed, although we are using a big one: CiviCRM with CiviMail enabled.
--
Jenni S.
I am having the exact same
I am having the exact same issue with Drupal 6.x I have increased memory to 64MB through the php.ini file. Yet I get this error:
Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 9564 bytes) in /hermes/bosweb/web145/b1458/ipw.###/public_html/dev/###/includes/image.gd.inc on line 190
Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 12 bytes) in /hermes/bosweb/web145/b1458/ipw.###/public_html/dev/###/includes/database.mysql-common.inc on line 34
The message says that you
The message says that you are running with 16M memory, so i am not sure it is the same issue. You can verify this by looking at the admin/reports/status page. I don't know which method you used to increase the memory, but obviously it didn't work.
Make sure that you specified
16Mand not16MB, and that you don't have another setting in Drupal's .htaccess or settings.php file which overrides the one in php.ini.Damn I didn't notice that.
Damn I didn't notice that. Turns out settings.php was overriding my php.ini settings.
Now once I hit 'insert' I get to a grey page where the header says: "Properties: Change how the image is displayed." but nothing else.
Some modules are very
Some modules are very greedy. For example, I have one site with 64M and imagecache module complains that it needs 96M to do image resizing. My current thinking is that I'd rather ditch that module from any site on a shared host at the first sign of trouble.