Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10900
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Mon, 5 Jul 2004 08:46:42 +0200 (CEST)
To: Gareth Ardron <gareth@fission.org.uk>
cc: internals@lists.php.net
In-Reply-To: <1088892609.2185.61.camel@mesa>
Message-ID: <Pine.LNX.4.58.0407050845580.2679@localhost>
References: <5.1.0.14.2.20040623142947.03cca8e0@localhost> 
 <5.1.0.14.2.20040623142947.03cca8e0@localhost>  <5.1.0.14.2.20040623170721.048dca08@localhost>
  <Pine.LNX.4.58.0407031233260.2646@localhost> <1088892609.2185.61.camel@mesa>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] 'make install' fails when --enable-memory-limit  is
 present
From: derick@php.net (Derick Rethans)

On Sat, 3 Jul 2004, Gareth Ardron wrote:

> On Sat, 2004-07-03 at 12:13, Derick Rethans wrote:
>
> > > > > My suggestion - add -dmemory_limit=32M to PEAR_INSTALL_FLAGS (16M solves
> > > > > the problem on my Linux box, but I think we should go higher to be on the
> > > > > safe side).
> > > >We prolly should highen the limit to a default 16M too for PHP 5.
>
> > Because applications in PHP 5 will most likely be larger usually due to
> > the better support for OO. People will earlier attempt to create more
> > complex applications and easily get over the low limit of 8MB.
> > Additionaly to this, you can't even resize a truecolor jpg (1600x1200)
> > at this moment with the default memory limit because GD uses about 4
> > times the amount of pixels in an image as memory.
>
> To be honest, I've never understood why. php_imlib2 seems to run though
> things fine with large files, and the structure of that is hardly
> uncommon, and it's not like I've been doing anything dodgy with fudging
> the zend api to get it to work right.

It was changed for a reason, that is that people could GD to crash
servers quite easily. Removing this restriction is not an option.

Derick