Bug #43757 [Com]: imagecreatefromjpeg error
| From: | rune dot waage at gmail dot com | Date: | Wed, 28 Apr 2010 16:49:48 +0000 |
| Subject: | Bug #43757 [Com]: imagecreatefromjpeg error | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-150000@lists.php.net to get a copy of this message | ||
Edit report at http://bugs.php.net/bug.php?id=43757&edit=1
ID: 43757
Comment by: rune dot waage at gmail dot com
Reported by: xfreelancer at yahoo dot com
Summary: imagecreatefromjpeg error
Status: Bogus
Type: Bug
Package: GD related
Operating System: CentOS
PHP Version: 5.2.5
Assigned To: pajoye
New Comment:
Hi,
is the problem solved?
I see that "xfreelancer at yahoo dot com" which reported the issue had
his memory limit set to 256Mb, and still the problem occured. So I don't
think the last post in this thread solved his problem.
I find it strange that when PHP tries to allocate 26320 bytes, the error
message tells you that you uses more then 33554432 bytes.
Previous Comments:
------------------------------------------------------------------------
[2008-01-25 18:26:16] pajoye@php.net
33554432 means around 33MB. Your images are 2186 x 2112, each image will
use around 24MB. That lets approximatively 8-9MB for all other PHP
operations. It is definitively a memory limit case and not a bug.
To confirm it, the images can be read by PHP and GD smoothly, with or
without memory_limit.
The solution is to increase your memory limit to the current default
128MB (it is the default for a reason).
------------------------------------------------------------------------
[2008-01-25 14:38:25] kiclaw at o2 dot pl
Here are two sample images causing this problem:
http://static.geozeta.pl/content/images/S601.JPG
http://static.geozeta.pl/content/images/S602.JPG
------------------------------------------------------------------------
[2008-01-13 01:00:00] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2008-01-05 11:47:24] pajoye@php.net
Please provide an example of images causing this problem, paste a link
to them here.
------------------------------------------------------------------------
[2008-01-05 06:01:25] xfreelancer at yahoo dot com
In case you need more information about our PHP voila phpinfo():
PHP Version 5.2.5
System Linux xxx.xx 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT
2007 i686
Build Date Dec 31 2007 13:26:06
Configure Command './configure' '--disable-all' '--with-pcre-regex'
'--enable-simplexml' '--enable-libxml' '--enable-session'
'--with-apxs2=/usr/local/apache2/bin/apxs' '--with-mysql'
'--enable-ftp'
'--with-config-file-path=/etc' '--with-freetype-dir=/usr/lib'
'--with-png-dir=/usr/lib' '--with-gd' '--enable-gd-native-ttf'
'--with-zlib' '--with-jpeg-dir=/usr/lib' '--with-gmp'
'--with-openssl'
'--with-pear' '--enable-xml' '--with-curl'
'--with-config-file-path=/etc'
Server API Apache 2.0 Handler
Virtual Directory Support disabled
Configuration File (php.ini) Path /etc
Loaded Configuration File /etc/php.ini
PHP API 20041225
PHP Extension 20060613
Zend Extension 220060519
Debug Build no
Thread Safety disabled
Zend Memory Manager enabled
IPv6 Support enabled
Registered PHP Streams php, file, data, http, ftp, compress.zlib,
https, ftps
Registered Stream Socket Transports tcp, udp, unix, udg, ssl, sslv3,
sslv2, tls
Registered Stream Filters string.rot13, string.toupper, string.tolower,
string.strip_tags, convert.*, consumed, zlib.*
AND
gd
GD Support enabled
GD Version bundled (2.0.34 compatible)
FreeType Support enabled
FreeType Linkage with freetype
FreeType Version 2.3.4
GIF Read Support enabled
GIF Create Support enabled
JPG Support enabled
PNG Support enabled
WBMP Support enabled
XBM Support enabled
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/bug.php?id=43757
--
Edit this bug report at http://bugs.php.net/bug.php?id=43757&edit=1