Hi there this is my first post, I hope M. Calguy will read.
I find CMS and Modules great to use.
Lately I have created an upload page using Uploads Module, I have 16mg of memory but still got memory errors on files with the jpeg and jpg extention.but none for others much heavier, here is the error message
Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 14668 bytes) in /*/*/*/*/public_html/lib/filemanager/ImageManager/Classes/GD.php on line 87
I noticed the GD class extention and tried removing the create thumbnail options in preference and see if it was the cause of the problem, after I removed all the extentions, the error sems to have gone, I thought I would share this.
Thanks again for the great oportunity you give us by providing this great software under the GPL.
(partly solved)uploads module memory problem with jpg but not other files
(partly solved)uploads module memory problem with jpg but not other files
Last edited by rocket on Sat Oct 06, 2007 4:58 pm, edited 1 time in total.
-
calguy1000
- Support Guru

- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: uploads module memory problem with jpg but not other files
Uploads module is a bit of a pig.... try changing your setting to 24mb.
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Re: uploads module memory problem with jpg but not other files
Thanks, for the reply, I will give it a try, but what I found strange was that the preferences included BMP for thumnails as well, but I never got an error even when uploading a 50mg BMP file, I only got the error message with jpg, jpeg.
Thanks
Thanks
Re: uploads module memory problem with jpg but not other files
I'll answer my own question here,
Obviously I didn't know but GD only deals with Jpg and png, so any other files extention will not be process it seems.
Obviously I didn't know but GD only deals with Jpg and png, so any other files extention will not be process it seems.
Re: (partly solved)uploads module memory problem with jpg but not other files
As far as the problerm with the fatal error, after I raised the PHP memory to 42mg, even 64mg, I still get the same error.
Fatal error: Allowed memory size of 44040192 bytes exhausted (tried to allocate 14668 bytes) in /*/*/*/*/public_html/lib/filemanager/ImageManager/Classes/GD.php on line 87
It seems that this error reporting is a bit off, as it advise to allocate 14668 bytes, but I have much more available.
I'm confused, maybe it's a bug somewhere in the classe.
Any ideas anyone.
latest cms, latest Uploads,
Apache 1.3.33
MySQL 4.0.17
Version PHP 4.3.10
Thanks
Fatal error: Allowed memory size of 44040192 bytes exhausted (tried to allocate 14668 bytes) in /*/*/*/*/public_html/lib/filemanager/ImageManager/Classes/GD.php on line 87
It seems that this error reporting is a bit off, as it advise to allocate 14668 bytes, but I have much more available.
I'm confused, maybe it's a bug somewhere in the classe.
Any ideas anyone.
latest cms, latest Uploads,
Apache 1.3.33
MySQL 4.0.17
Version PHP 4.3.10
Thanks
Last edited by rocket on Sat Oct 06, 2007 11:51 pm, edited 1 time in total.
Re: (partly solved)uploads module memory problem with jpg but not other files
I would like to know if anyone has had this problem before.
Should I file a bug report, and if so is this a Core problem or a Uploads problem.
We are talking about a fatal error even at 64m of php memory. Obviously something is wrong somewhere.
Thanks
Should I file a bug report, and if so is this a Core problem or a Uploads problem.
We are talking about a fatal error even at 64m of php memory. Obviously something is wrong somewhere.
Thanks

