Bug #12634 Updated: Segfaults due to possible memory leak??
| From: | lobbin@php.net | Date: | Wed, 02 Jan 2002 19:00:39 +0000 |
| Subject: | Bug #12634 Updated: Segfaults due to possible memory leak?? | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-75648@lists.php.net to get a copy of this message | ||
ID: 12634
Updated by: lobbin
Reported By: katz@advanced.org
Old Status: Feedback
Status: Closed
Bug Type: Reproducible crash
Operating System: Linux 2.4
PHP Version: 4.0.6
New Comment:
No feedback. Closing.
Previous Comments:
------------------------------------------------------------------------
[2001-12-12 04:13:50] yohgaki@php.net
Status = Feedback
------------------------------------------------------------------------
[2001-12-12 04:08:45] yohgaki@php.net
Do you still have problems with 4.1.0?
Is it ok to be closed?
------------------------------------------------------------------------
[2001-10-03 14:21:36] katz@advanced.org
As a follow-up on this bug report .. Just today I installed a recent cvs version (called
"4.0.7RC2" in the Debian unstable distribution)...
So far the system has been running almost an entire day without a problem .. I noticed in the change
log that there were some LDAP memory leak fixes ... that may have been the problem as our site also
relies heavily upon ldap ..
So far .. So good.
------------------------------------------------------------------------
[2001-08-19 21:40:28] katz@advanced.org
Also .. keep in mind my stuff uses OCI-8 (with oracle 8.1.6), so that may be linked (since no one
else has reported this problem).... ??
------------------------------------------------------------------------
[2001-08-19 21:36:48] katz@advanced.org
No, it appears to be almost random.... The script names (and line numbers) that appear in the logs
are always different.
I was able to force the problem for any script by using the apache benchmark utility (ab) and
blasting a script with generated hits .. when doing this the seg faults start almost immediately
(and again for any php script i point it at).. if this helps....
------------------------------------------------------------------------
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/?id=12634
Edit this bug report at http://bugs.php.net/?id=12634&edit=1