ID:               36084
 Updated by:       [EMAIL PROTECTED]
 Reported By:      clive at darkarts dot co dot za
-Status:           No Feedback
+Status:           Feedback
 Bug Type:         Reproducible crash
 Operating System: FreeBSD
 PHP Version:      5.1.2
 New Comment:

Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32

Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.




Previous Comments:
------------------------------------------------------------------------

[2006-02-25 10:57:04] kama at pvp dot se

This is not really related to imagick. I have got the issue without
imagick installed. If I change which extentions I install, phpinfo()
will crash in different places.

At first I thought it was a bug in how much data was sent, but after
sending 200 tables with 40 rows in each I concluded this was not the
problem.

My initial thought was that it has something todo with the plugin api.
I have never looked at the source, so this is just a wild guess that it
crashes when it query the plugin/extention.

I cvsuped back to 5.0.5 in the portstree and all problems dissappeared.
Everything else is the same, I just downgraded php5.

------------------------------------------------------------------------

[2006-02-06 00:26:38] yvovandoorn at comcast dot net

I recompiled pecl-imagick on both machines and it still doesn't work. 

I did make deinstall -> make clean -> make install. 

Error message:
php -i
...
imagick

ImageMagick support => enabled
Magick Backend => ImageMagick
ImageMagick version => 6.2.5
PHP imagick version => 0.9.11
MaxRGB => 65535
Supported image formats => 8BIM
php in free(): error: junk pointer, too high to make sense
Abort (core dumped)

------------------------------------------------------------------------

[2006-02-05 10:59:29] ale at FreeBSD dot org

Have you recompiled pecl-imagick after php update? I have no problems:

%php -v
PHP 5.1.2 (cli) (built: Jan 30 2006 17:07:55)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies

%php -i
...
imagick

ImageMagick support => enabled
Magick Backend => ImageMagick
ImageMagick version => 6.2.5
PHP imagick version => 0.9.11
MaxRGB => 65535
Supported image formats => 8BIM
Font Family - Name => AvantGarde - AvantGarde-Book
...

------------------------------------------------------------------------

[2006-02-05 07:13:08] yvovandoorn at comcast dot net

I'm pretty sure this isn't related to Apache2. The reason why is that I
am experiencing this problem on two machines, one installed with FreeBSD
5.4 and the other FreeBSD 6.0. The only thing these two have in common
is that I installed all my additional applications via the ports.

On both machines the problem goes away the moment I disable the
imagemagick extension. Yes both machines are running Apache2, however
this problem appeared before php 5.1.2, but sometime a week after the
new year.

Since I strongly believe that the imagick extension is the cause of it,
I did some checking and found out the port was upgraded for pecl-imagick
on 01/05/06 so I'm pretty sure thats where the issue lies. 

I've contacted the maintainer for that port (and strangely he also
maintains php5 & php5-extensions).

------------------------------------------------------------------------

[2006-02-03 12:20:50] mail at skraemer dot net

This might help you:

I ran into the same problem, and the error dissapeared when i commented
out the "ImageMagick"-extension in my "exentsions.ini"
(FreeBSD-system).

If you need detailed informations about the cofiguration- /
compiling-process, please send me an e-mail.

------------------------------------------------------------------------

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/36084

-- 
Edit this bug report at http://bugs.php.net/?id=36084&edit=1

Reply via email to