Memory error while uploading

[WARit]

Hello, after reinstalling a fresh 1.6 version, I'm getting this error while importing some new images:


Fatal error: Allowed memory size of 52428800 bytes exhausted (tried to allocate 3456 bytes) in /srv/vhosts/www.domain.com/www/administrator/compon ... lpers/phoc agallery.php on line 408

Any help?

[WARit]

Update: now I'm stuck on that error page accessing phogallery component, it just changes the (tryed to allocate xxxx bytes).

It seems that the component still looping on something not recognizable.

[Jan]

Thank you for your info, the error handling is not complete yet, because I cannot simulate all errors which are caused by thumbnails creating...

So if it is possible (it is a test site e.g. and you can change the ftp password), and you send me these passwords I can test it on your server....

Jan

[WARit]

Well it's quite "unsecure" for me to provide you the ftp password I'm using atm (mainly because with it I can manage different domains).
But I'm on call with the host admin, he raised the http memory limit to 128mb and the problem still stand there.
He said to me that usually any upload via http (despite the fact that I don't know what phoca is doing with my ftp files during the process of creating thumbnails and categorizing them) will triple the memory usage displayed on the error message. On top of them add the memory used to thumbnail themself.
In this particular issue, the images I've tryed to upload are five, with an overall dimension of almost 6 mb (all together, while each file is siezed by 2mb to less than a mb).

I hope it can help

[Jan]

???
The problem on 408 is:

ImageCreateFromJPEG() - GD function which returns error while creating thumbnail on your server...It doesn't depend on HTTP redirect. So your GD doesn't have enough memory (??) or there is something wrong with the GD library...

???

[WARit]

PHP Built on: Linux ftw 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC x86_64
Database Version: 5.0.45-Max
Database Collation: utf8_general_ci
PHP Version: 5.2.5
Web Server: Apache/2.2.4 (Linux/SUSE)
Web Server to PHP interface: apache2handler
Joomla! Version: Joomla! 1.5.1 Production/Stable [ Seenu ] 8-February-2008 22:00 GMT
User Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12

[WARit]

Ah ok I will forward the information to my host admin, thanks for the support!

[Jan]

The same as I have on my Suse Linux 10.3 localhost, but as I wrote the problem will be with (maybe) GD x Memory

[WARit]

Ok news from the front, the host admin says that:


your module set a limit: ini_set('memory_limit', '50M') that overrides the server settings (actually at 128mb).

That means that I have to upload images smaller that before the 1.6 version.
To calculate the real image in byte we have to apply this simple formula
height x width x 24 / 8 = dimension in bytes used by the script
It means that 1680x1050 takes 5mb of memory. If this image will be used to create previews (GD?) the memory is multiplyed by 3.
Now the host admin doesn't know if the script is optimized to free the memory space before step ahead to another image.

Actually, just one of the images I'm trying to upload could exhausts the memory (50mb) and stuck the component in it's fatal error loop.

I can change the parameters in the script to enlarge the memory limit, but with the next componant upgrade I will get back to the same issue (if this is the right issue to fix).

[Jan]

If you go to the next site via HTTP, new script will beginn and the memory will be free, but the problem can be in GD module which could not catch free all memory...

- Yes the ini_set('memory_limit', '50M') I can change but I don't know what should say webhosting providers...