Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47453
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.216 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=C5kkS791cU0/4XxCFgxa9n+zPyi01go0YGZXv2qUdJRKfly5FsjWigPeuutwnzWAWJ
         9fqTqCu5fku7Gw3M+9cGMmaNB5oHrQ9YnorknZBb5/nBrgj6LFWGyOkMtmypFhA2WrMS
         R8AicS7yy1dHKa4Du7OK9PCQ+easIrkrV/wqY=
MIME-Version: 1.0
In-Reply-To: <f658eb6f1003220841p5517561cpd044d4389f7a3b63@mail.gmail.com>
References: <98b8086f1003220751j73a8414es89b9b469c46f6630@mail.gmail.com>
	 <1269270852.1575.141.camel@guybrush>
	 <98b8086f1003220822s47665f87x696b70e9c13dadbd@mail.gmail.com>
	 <f658eb6f1003220841p5517561cpd044d4389f7a3b63@mail.gmail.com>
Date: Mon, 22 Mar 2010 16:55:57 +0100
Message-ID: <b54d0abe1003220855v7164b8dcj3e5ea14d7896df67@mail.gmail.com>
To: Herman Radtke <hermanradtke@gmail.com>
Cc: troels knak-nielsen <troelskn@gmail.com>, 
	PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=00032555a0ca9a89b2048265bbcb
Subject: Re: [PHP-DEV] [PATCH] Raise warning first on "Maximum execution time 
	exceeded"
From: tyra3l@gmail.com (Ferenc Kovacs)

--00032555a0ca9a89b2048265bbcb
Content-Type: text/plain; charset=UTF-8

On Mon, Mar 22, 2010 at 4:41 PM, Herman Radtke <hermanradtke@gmail.com>wrote:

> > What do you mean by "no option"? Otherwise yes, that's what it does.
> Using sleep there is not a good practice.  Since the custom error
> handler is triggered, there is no need for the sleep call anyways.
>
> > I'm not sure I understand. Are you implying that it is somehow
> > possible to circumvent the second (fatal) error with this change? How?
>
> Consider for a second what you are asking the language to do.  The
> script has run out of memory and instead of halting you want it to
> switch into an error handler to log the error.  What happens when that
> error handler creates new variables or an object instance?  Where does
> that memory come from?
>
> The out of memory is a good example, but not the only one.
If you reached the memory limit, but the system has available memory, then
it should be handled with a soft limit/hard limit.

> A better solution: generate a warning for scripts that use some target
> % of memory.  I hate to add more ini settings, but for simplicity
> there could be a "memory_limit_warn" setting which you can set to
> something like "95%".  When a script reaches that memory threshold it
> can trigger a warning so you can log it.
>
you can write that in userland with memory_get_usage.
but its just one case from the many.

Tyrael

>
> --
> Herman Radtke
> hermanradtke@gmail.com | http://hermanradtke.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--00032555a0ca9a89b2048265bbcb--