#23455 [Opn->Fbk]: Memory Leak
| From: | helly@php.net | Date: | Sun, 01 Jun 2003 17:17:31 +0000 |
| Subject: | #23455 [Opn->Fbk]: Memory Leak | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-40823@lists.php.net to get a copy of this message | ||
ID: 23455
Updated by: helly@php.net
Reported By: adam at planetzerep dot com
-Status: Open
+Status: Feedback
Bug Type: Apache2 related
Operating System: Windows 2000
PHP Version: 4.3.2RC2
New Comment:
Please try using this CVS snapshot:
http://snaps.php.net/php4-STABLE-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php4-win32-STABLE-latest.zip
Previous Comments:
------------------------------------------------------------------------
[2003-05-17 22:47:11] adam at planetzerep dot com
Is this still being looked at?
------------------------------------------------------------------------
[2003-05-07 23:17:18] adam at planetzerep dot com
OK, I downloaded
http://snaps.php.net/win32/php4-win32-STABLE-200305071630.zip
It looks like there's still a leak... I ran apachebench:
Apache @ start: 16,988K memory
Apache after 50,000 requests: 30,856K memory
Apache after 100,000 requests: 33,592K memory
Apache after 150,000 requests: 36,336K memory
Apache after 200,000 requests: 39,076K memory
So it seems to be leaking about 56 bytes per request.
------------------------------------------------------------------------
[2003-05-07 09:16:31] moriyoshi@php.net
Try the latest cvs snapshot that will be available on May 07, 2003
16:30 GMT.
------------------------------------------------------------------------
[2003-05-06 18:42:40] adam at planetzerep dot com
This memory leak is not caused by apache "warming up" - I have left
apachebench running overnight, and apache will consume all of the
memory on the server.
------------------------------------------------------------------------
[2003-05-05 15:07:23] moriyoshi@php.net
related to bug #21283
------------------------------------------------------------------------
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/23455
--
Edit this bug report at http://bugs.php.net/?id=23455&edit=1