Fatal Memory Error
morten.kongsgaa... - April 14, 2009 - 13:14
| Project: | Fast Gallery |
| Version: | 6.x-3.3-beta1 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I get this error and can't figure out what is wrong
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 12288 bytes) in C:\xampp\htdocs\drupal\modules\fast_gallery\fast_gallery.cache.class.php on line 50
I have checked that there is no foldernames with space or forbidden carracters, but there is space in filenames. I have tried with two folders with subfolders with filenames with space and it works, but when I try to put in more folders it won't work. Is this a known bug? Is there a solution?
#1
#2
All of a sudden, I get the same error in 4.0b4
#3
Probably php.ini doesn't have enough memory allocated...
But, many hosting environments throttle your memory even if you try to allocate more.
#4
me to having the same problem on uploading images on image module..
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 12288 bytes) in C:\xampp\htdocs\travel\includes\image.gd.inc on line 190
#5
@ #3: No, php.ini DOES limit me, but to 150 MB. Error says something smaller than that threshold...
#6
My second point, above needs to be understood.
Although php.ini permits you to set your memory limit as high as you want, some hosting service throttle you to much less. Specifically for example, Blue Host has a limit at 30k or 50k. They won't quite tell you what it is, and when I ask other hosting services I also get a run-around or else professed ignorance. 30k could end up with your 33k limit given the difference between k bits and 1024 bits.
Certainly, Drupal developers need to pay attention to memory usage, especially as we assemble drupal installations with many modules. Views and CiviCRM are quite heavy. You could try cutting off one of those to see if it helps.
I also find that memory issues can be inconsistent. One set of modules causes a memory conflict, but on another day it doesn't. Or, loading a module causes a memory error, but the second time you load it, things are fine.
Some bulk load modules choke when they get too many entries uploaded at once. I don't know if this is the case with fast gallery.