On Thu, Mar 12, 2015 at 1:46 AM, Stanislav Malyshev <smalys...@gmail.com> wrote:
> Hi! > > > I think, after "max_execution_time" is exceeded, we may start another > > "hard_timeout", and in case the EG(vm_interrupt) wasn't handled > > "safely", kill the process. > > I remember such proposal floating on the list recently, with two-stage > timeouts. But wouldn't killing the process run the same risk that it > left something messed up in SHM? > yes :( if we try to recovery from some inconsistent state we most probably crash. I even don't talk about memory and resource leaks. > Also, in threaded environments that's probably not an option, and PHP > may not even own the thread. > I'm not sure how the existing setjmp/longjmp based timeout handling works in ZTS environment now, because except of SHM it may also easily corrupt the process memory shared with other threads. Thanks. Dmitry. > > -- > Stas Malyshev > smalys...@gmail.com >
