By vigoritor on
Hello i am trying to access blocks from the admin screen. I get 'fatal error: allowed memory size exhausted'...
.... i have read tons of threads w/ this problem all say to increase the memory size in settings.php or .htaccess...
i have done both and raised it as high as 40M. Still the same problem.
Curious as to how high i should be attempting this in that most people were saying 12M or 16M also i find it strange that this is happening when im accessing blocks.
Any ideas?
Thanks,
-rich m
Comments
Ask your webhost company how
Ask your webhost company how to increase php's memory limit. Some don't allow an increase via .htaccess or via settings.php. I know this is the case on Site5's shared hosting platform.
That's where I would start.
phpinfo
You might want to see if your updates were processed. You can either do your own phpinfo() or use the DEVEL module's link to phpinfo() to see what the actual memory assignments are. As the other poster mentioned, your hosting may have disabled your ability to use the override, and you may still be using the default.
-------------------
http://www.PrivacyDigest.com/ News from the Privacy Front (Drupal)
http://www.SunflowerChildren.org/ Helping children around the world ( Drupal)
let first say thanks for the
let first say thanks for the replies they didnt go unnoticed just had unforeseen things take me away from this project. ... anyways i did do phpinfo and my changes were accepted and setting to 40MB is now the current. however i still have the issue w/ exhausted memory when accessing blocks and now i can only upload images somewhere under 1MB even though my drupal file attachment setting is 4MB and my image attachment is at currently at 2MB. .... wierdness/confusion/frustration w/ memory issues. any and all insight or thoughts would be greatly appreciated.
thanks,
rich
You don't mention the exact
You don't mention the exact msg that you get when your image fails to upload. Do you get an error during the actual upload or do you just have it not display later? I ask, since when I first started I was getting memory error when accessing a photo that seemed not to upload, but had actually been uploaded but just couldn't display. In my case the problem was imagecache. When it went to resize the photo for display it ran out of workspace. I don't know the exact multiplier, but the workspace required was a multiple of the photo size.
-------------------
http://www.PrivacyDigest.com/ News from the Privacy Front (Drupal)
http://www.SunflowerChildren.org/ Helping children around the world ( Drupal)
I dont get a message which
I dont get a message which really sucks... also too the image doesn't get uploaded. the file isnt in /files/images nor is the node created. The page just refreshes to the image node creation form page.
Hmm ... that IS really
Hmm ... that IS really strange. nothing in Watchdog or the Apache logs. I'm guessing that you did this but have to ask since I have seen a client make this mistake. After selecting the file to upload(via the open box called by the Browse button) you did hit the Upload button, right? and then you should get a thumbnail view and then you save the whole page?
-------------------
http://www.PrivacyDigest.com/ News from the Privacy Front (Drupal)
http://www.SunflowerChildren.org/ Helping children around the world ( Drupal)
the version of drupal
the version of drupal (5.Something) and probably more specifically version of image module doesn't have an upload button. just a place to browse to the file, then i have been hitting submit. i did notice that file attachment has an 'attach' button but i am using image module for my purposes. previously i could submit images as i have submitted many others until this madness. also a weird turn of events i used to be able to submit smaller file size pics (>1MB) just fine but now even for the smaller ones i am running into that exhausted memory message:
Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 14592 bytes) in bla/bla/bla/html/includes/image.inc on line 308
some ideas
You might want to check out this thread. It seems to mention a few diff things to check.
http://drupal.org/node/171696
One is that the Image module has its own limits that might be getting in the way, even if your global has lots of room.
-------------------
http://www.PrivacyDigest.com/ News from the Privacy Front (Drupal)
http://www.SunflowerChildren.org/ Helping children around the world ( Drupal)