Fatal error: Allowed memory size "exhausted"

[DefenceTalk.com]

Uploading image and got this error:

Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 8000 bytes) in /home/defence/public_html/pictures/image-inc.php on line 115



Running the latest version5.13 of pp.

[Chuck S]

Okay your php memory is exhausted.

You can try in uploadphoto.php right under the line

require "pp-inc.php";

add

ini_set("memory_limit", "40M");

[DefenceTalk.com]

Thanks.

Now, getting error if user tries to upload buld uploads or 5 allowed uploads.

[Chuck S]

Okay same error?

How does a user have bulkupload capability?

[DefenceTalk.com]

well, if its more than one pic then it gets to the page where you can set title and description of the image (Add Photos - Select Photos / Configure Properties ) but then gives this error:
Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 8000 bytes) in /home/defence/public_html/pictures/image-inc.php on line 115

[Chuck S]

Okay same thing you did in uploadphoto.php do to bulkupload.php

[Swanny]

This is happening to me in 5.31. It just happens to me (admin). It doesn't happen to any regular users. It just started happening a few weeks ago.

I added the ini_set line in uploadphoto.php and I still get the error:

Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 20000 bytes) in /home/fusion/public_html/photos/image-inc.php on line 99

[Chuck S]

Okay is your uploads directory clogged with images not processed?

[Frank Woolf]

I have been experiencing the same problem and it started when my hosting company recently installed bug fixes to PHP 5.2.1. The first obvious problem was that most pages of all sites using PHP would not load. then later I discovered nobody could upload pictures of more than a few KB in ppClassifieds or Photopost. I have copied part of the hosting company's last reply below:

This is nowhere near a good enough solution as people have got used to uploading up to six images as big as 2mb each. I will need to make some drastic changes to what users are allowed to upload.

If anyone has a better solution I would love to know about it.

I was able to upload some decent sized images after setting the server limits to 32Mb. I had some trouble with the 650Kb image but then I cleared out their 'uploads' folder of the unprocessed stuff (as suggested by the photopost developers) and then it went through just fine. I think that this software isn't making smart use of the conversion and that's why it's wanting to allocate 90Mb just for some larger images. I'm sorry but we just aren't willing to increase the memory limits any higher than 32Mb as this is a shared hosting environment.

The reason that this would have started happening after February 21st is because of the bug fixes to PHP 5.2.1 where it actually *started* enforcing the memory limits that were in the server config. What may seem like a bug at the server level now is actually a bug fix, and is in fact the software beginning to work properly.

[Chuck S]

Your recourse would be to have your company tell you or install Imagemagick for you. We have no control over GD2 which is part of PHP or how much memory it requires to process images. Thats a server issue with GD2 and PHP so all we can suggest for those using GD2 is to increase PHP memory or switch to Imagemagick(mogrify)

[Frank Woolf]

Many thanks Chuck.

I have passed your message on to the hosting company. I have often thought that Imagemagick should be installed.

[Chuck S]

Yeah it is GD2 using up the PHP memory since it is part of PHP so not much you can do other than restrict filesizes if they wont change anything or get them to install Imagemagick or move to a host that has imagemagick

[Frank Woolf]

According to my hosting company Imagemagick is installed. They told me to change the path to mogrify from "/usr/bin/X11/mogrify" to "/usr/bin/mogrify"

I tried that and still get the same error message.

Is there somewhere in Photopost where I should change GD to Imagemagick? I can't find anything other than the path in the control panel or config.inc

[Frank Woolf]

Sorry Chuck I found the GD/Imagemagick selection in the control panel. I am too tired to see straight.

I changed to Imagemagick and tried uploading. I got the following error:

Error creating thumbnail! Error code: 1

Command:

"/usr/bin/mogrify" +profile "*" -size 150x100 -quality 60 -geometry 150x100 -unsharp 10 '/home/carsales/public_html/photopost/data/500/thumbs/100_0905.JPG'

Can you advise please?

[Frank Woolf]

Found the solution by searching through related posts. I deleted +profile \"*\" from image-inc.php and it worked

[Quarterbore]

I have been fighting with this memory issue for a while as well. I am curious about the question about the "uploads" folder above and should I delete the images in there to try to resolve this?

Also, do I understand correctly that moving to Imagemagic will help resolve this issue?

I have somewhere around 7,000 members and to my knowledge I have five members that get this error but they get the error every time they try to upload an image.

Nobody else sees it so I am stumped.

-- EDIT 1 ------------

Edit - I have decided to switch my Photpost to use ImageMagick (I do have it on my server) and I changed the setting in:

adm-misc.php >> Photopost options

When I try to upload an image I get this error:

Error creating thumbnail! Error code: 127

Command:

"" +profile "*" -size 150x143 -quality 70 -geometry 150x143 -unsharp 10 '/home/quarterb/public_html/photopost/data/500/thumbs/homersbrain300.jpg'

What am I missing?


-- EDIT 2 -----------

*** Things I have tried:
In Config - Tried adding Imagemagick path in setting for Path for MOGRIFY executable (/usr/bin) and that did not help. (Should that have a value?)

---- EDIT 3 - LAST EDIT --------

OK, I found the following thread:

Error code: 127 - Please Help

In there was this tidbit:

So I researched here and found my Path for MOGRIFY executable it is set to

/usr/bin/mogrify

When I added this to my Config the new error went away. I am waiting for my few members that could not upload to advise if moving to ImageMagick solves the error they had in the first place.

[Chuck S]

You can delete the numeric directories under uploads folder yes

Your other errors where just because you did not have the proper path to imagemagick in the config.

you can also bump up memory for php like so

http://www.photopost.com/forum/1219346-post2.html

[stmpspaz]

I have read the posts here - but since they are about a year old I just wanted to verify that it is safe to delete all the numbered directories in the uploads directory. (including the 0 directory)

We are using version 6.23

[Chuck S]

Yes it is safe to delete anything under the uploads directory. Processed images are under data so thats what you dont want to delete.