#16820 [Fbk->Opn]: hangs in multithreded environment (ZTS)

From: Date: Fri, 11 Jul 2003 08:15:06 +0000
Subject: #16820 [Fbk->Opn]: hangs in multithreded environment (ZTS)
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-43742@lists.php.net to get a copy of this message 
 ID:               16820
 User updated by:  wmeler at wp-sa dot pl
 Reported By:      wmeler at wp-sa dot pl
-Status:           Feedback
+Status:           Open
 Bug Type:         Scripting Engine problem
 Operating System: linux
 PHP Version:      4.3.0-dev
 New Comment:

that funny restrictions ... try this:
http://strony.wp.pl/wp/wmeler/execution-timeout.patch.html


Previous Comments:
------------------------------------------------------------------------

[2003-07-11 02:54:49] sniper@php.net

That url gives 403..was it incorrect..?


------------------------------------------------------------------------

[2003-07-11 02:40:47] wmeler at wp-sa dot pl

script like:
<?
set_time_limit(1);
while (TRUE) {
   $a.='a';
}
?>

should hang server in ZTS mode on linux after few reloads.

You can download my patch from

http://strony.wp.pl/wp/wmeler/execution-timeout.patch

It is for erlier version, but it applies with offsets.

------------------------------------------------------------------------

[2003-07-10 19:54:27] sniper@php.net

Can you please provide either a testcase for this so we can actually
reproduce this or a patch to fix it?


------------------------------------------------------------------------

[2002-10-21 11:19:40] sniper@php.net

Updated version info. (assuming the last comment was based on the
snapshot)


------------------------------------------------------------------------

[2002-10-21 00:18:54] wmeler at wp-sa dot pl

Well, it seems that nothing has changed - on timeout it still does
longjmp without care of semaphores. Locks won't be freed so it will
hang. 
As I wrote few months ago, signal handler should only set EG(timeout)
flag.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/16820

-- 
Edit this bug report at http://bugs.php.net/?id=16820&edit=1

Thread (39 messages)

« previous php.bugs (#43742) next »