Bug #13970 Updated: possible deadlock?
| From: | jpm@php.net | Date: | Tue, 18 Dec 2001 14:54:36 +0000 |
| Subject: | Bug #13970 Updated: possible deadlock? | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-74255@lists.php.net to get a copy of this message | ||
ID: 13970
Updated by: jpm
Reported By: fuf@mobil.cz
Old Status: Open
Status: Closed
Bug Type: Performance problem
Operating System: linux, kernel 2.2.x
PHP Version: 4.0.6
New Comment:
Status -> closed.
Previous Comments:
------------------------------------------------------------------------
[2001-12-18 09:53:43] fuf@mobil.cz
4.1.0 works all okay - i've encoutered no strange behaviour.
thanks for the good work!
Michal Vitecek
------------------------------------------------------------------------
[2001-12-12 19:14:35] yohgaki@php.net
Could you try PHP 4.1.0 see if it help? and report the result?
------------------------------------------------------------------------
[2001-11-07 06:29:06] fuf@mobil.cz
okay - i tried with php4-200111070000. no luck though because there were some other issues:
- compilation problems (the configure script wrongly thinks that gdImageColorResolve is undefined
in gd-2.0.1)
- stability problems (the apache children segfaulted - one each ~3 secs)
- other problems (this version claimed that some files couldn't be stated because of
permissions - apparently wrong because the files are created by the same user that reads them and
are normally accessible + no problems with 4.0.5-6).
------------------------------------------------------------------------
[2001-11-07 05:45:22] rasmus@php.net
Any chance you could test the current CVS code? Snapshots are available from http://snaps.php.net
------------------------------------------------------------------------
[2001-11-07 05:28:04] fuf@mobil.cz
hello,
with php 4.0.6 apache stops responding after 3-12 hours of working whereas with 4.0.5
everything's okay. it definitely looks like some kind of a deadlock and it's unpredictable
when the it happens.
php is compiled with these options:
CFLAGS="-O6 -march=i686 -fomit-frame-pointer" \
./configure \
-with-sybase-ct=/home/sybase \
--enable-sysvsem \
--enable-sysvshm \
--enable-memory-limit \
--enable-sockets \
--disable-session \
--with-gmp \
--with-dbase \
--with-gd \
--enable-gd-native-ttf \
--with-freetype-dir=/usr/local \
--with-jpeg-dir=/usr \
--with-png-dir=/usr \
--with-zlib-dir=/usr \
--without-mysql \
--with-apache=../apache
the same bad behaviour occurs with php compiled as a standalone aplication when the script runs for
a longish time.
the memory-limit patch for 4.0.6 was installed.
thanks
Michal Vitecek
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=13970&edit=1