Re: [PATCH] Raise warning first on "Maximum execution time exceeded"

From: Date: Mon, 22 Mar 2010 15:55:26 +0000
Subject: Re: [PATCH] Raise warning first on "Maximum execution time exceeded"
References: 1 2 3 4  Groups: php.internals 
Request: Send a blank email to internals+get-47452@lists.php.net to get a copy of this message
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.

So control isn't returned to the C-code before the php error handler
finishes. Is that it?

On Mon, Mar 22, 2010 at 4:41 PM, Herman Radtke <hermanradtke@gmail.com> wrote:
> 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?

This patch handles timeout, not memory exhaustion.

Although a similar solution for memory exhaustion could be useful as well.

-- 
troels


Thread (26 messages)

« previous php.internals (#47452) next »