#21283 [NoF]: memory leak under Apache2

ID: 21283 Updated by: moriyoshi@php.net Reported By: tamagawa at osa dot att dot ne dot jp Status: No Feedback Bug Type: Apache2 related -Operating System: Windows 2000 Server (Japanese) +Operating System: Windows XP Home Edition PHP Version: 4.3.1 New Comment: update version Previous Comments: ------------------------------------------------------------------------ [2003-05-05 15:09:30] moriyoshi@php.net grrrr bug #23455 ------------------------------------------------------------------------ [2003-05-05 15:08:52] moriyoshi@php.net Related to bug #2345 (The summary and the OS entry were unexpectedly changed.. weird..) ------------------------------------------------------------------------ [2003-04-02 10:56:57] sniper@php.net No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2003-03-26 22:43:34] ianh@php.net Hi Tamagawa. we've done a big change in the apache2 <--> php interface in the current CVS head, which may have helped with your issue. please note that apache will grow in memory usage for a while it is still warming up, until it peaks out (due to the way it uses pooled memory) is it possible you are seeing this? the way to test this is if you keep seeing a increasing memory utilization after say a 30-40 minutes of hitting your server with a constant load. regards ian ------------------------------------------------------------------------ [2003-02-12 23:40:29] tamagawa at osa dot att dot ne dot jp Simply doing - h.putrequest('GET', '/test.php') + h.putrequest('GET', '/index.html.en') stops leaking. (Hope this is the right way to reply my own report...) ------------------------------------------------------------------------ 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/21283 -- Edit this bug report at http://bugs.php.net/?id=21283&edit=1