Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:27832
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.162.230 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=ioTnr0MjH/hP6zQSFaKEyJc8MuFgZDcLbFxe8ycTQljlOCn/4HTi74sfOOoAReYv3uJlRTkFHOoEDjQYGixSjT+Fx8VZV8emAGAOsNME1ZtpSUdQ2ClbywYionnTwNYRVyZ4suUgBIUYVEMKm6h8VIiY5qBiAc+0HtJBzS/ROig=
Message-ID: <fe05d1540702051340g54d7f4cfo9627f70e48f3ff4f@mail.gmail.com>
Date: Mon, 5 Feb 2007 22:40:23 +0100
To: "Reinis Rozitis" <r@roze.lv>
Cc: internals@lists.php.net
In-Reply-To: <010c01c7496b$33d9d270$698df657@wired>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <006d01c74961$ae34f4f0$698df657@wired>
	 <fe05d1540702051237t35c5147av94a78e684a6cac61@mail.gmail.com>
	 <010c01c7496b$33d9d270$698df657@wired>
Subject: Re: [PHP-DEV] FastCGI limit memory
From: pierre.php@gmail.com (Pierre)

Hi,

On 2/5/07, Reinis Rozitis <r@roze.lv> wrote:
> > It will never replace the GD extension. Please read the whole thread
> > before making conclusions (btw, check out http://www.libgd.org).
>
> I didnt mean that way nor as a conclusion, GD is still much faster and so on
> (but thanks for the link/hint).

Keep an eye on the current 2.1.0 development, it will be really fast :)

> It was just an excuse why did I play with magickwand (what Thomas proposed)
> in case somebody would ask why there is a need for such feature and just
> respond with "we dont support third-party extension.. if it breaks core then
> its your own fault" ;)
>
> Aye the lighty stats look "fishy" (lets wait march) but whatever its
> something Netcraft provides..
>
>
> Besides getting comments on all other parts but not the initial question? :)

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.

Note to anyone, please correct me if I'm mistaken :)

--Pierre