Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:27833 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35687 invoked by uid 1010); 5 Feb 2007 22:16:02 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 35672 invoked from network); 5 Feb 2007 22:16:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Feb 2007 22:16:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=r@roze.lv; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=r@roze.lv; sender-id=pass Received-SPF: pass (pb1.pair.com: domain roze.lv designates 80.232.169.231 as permitted sender) X-PHP-List-Original-Sender: r@roze.lv X-Host-Fingerprint: 80.232.169.231 kc.118.lv Linux 2.4/2.6 Received: from [80.232.169.231] ([80.232.169.231:27397] helo=kc.118.lv) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5C/D9-61367-1ACA7C54 for ; Mon, 05 Feb 2007 17:16:01 -0500 Received: from wired (unknown [87.246.141.105]) by kc.118.lv (Postfix) with SMTP id F2A95320002 for ; Tue, 6 Feb 2007 00:15:56 +0200 (EET) Message-ID: <015701c74973$32b61950$698df657@wired> To: References: <006d01c74961$ae34f4f0$698df657@wired> <010c01c7496b$33d9d270$698df657@wired> Date: Tue, 6 Feb 2007 00:15:52 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Subject: Re: [PHP-DEV] FastCGI limit memory From: r@roze.lv ("Reinis Rozitis") > I'm not sure that you are looking at the right place to solve the > problem. If the leaks are in phpinfo (or in memory allocated by php), > then maybe (really not sure). > > But if the leaks are in IM as their extension does not use php memory > manage, it is not something fixable by php or anything else but IM. Pierre you are getting me totally wrong. I dont really care for this particular ImageMagick(Wand) or even phpinfo leak at all :) What I am talking about is a feature which similar as 'memory_limit' (inside one script runtime) limits maximum memory usage for a long running php child (if spawned with the -b option (external FASTCGI Server mode)). At the moment the only option to avoid memory leaks is to set PHP_FCGI_MAX_REQUESTS after which the child dies and a new is spawned. Still the memory usage can grow (as example in this case) way too quick to actually hit the request limit, which may bring the system in OOM state. The patch was provided for 4.x branch http://www.zend.com/zend/week/pat/pat48.txt So I wanted to get some feebacks (without filling the feature request at bugs.php.net which I apologise for) if its something worth to implement. Probably to hear something from Dmitry. > Keep an eye on the current 2.1.0 development, it will be really fast :) Is the source allready available for testing? Those 3 remaining tasks in roadmap didnt look problematic at this state (though I suppose there are more issues).. rr