ID: 17268 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: Bogus Bug Type: Scripting Engine problem Operating System: Linux 2.4 PHP Version: 4.2.1 New Comment:
Not a bug In PHP -> bugs Previous Comments: ------------------------------------------------------------------------ [2002-05-27 16:52:35] [EMAIL PROTECTED] Sorry, the problem was related to ZendOptimizer 1.3.0. It works fine by just replacing 1.3.0 by 1.3.1. ------------------------------------------------------------------------ [2002-05-17 09:04:23] [EMAIL PROTECTED] Can you provide more details on your setup please? I'm not able to reproduce this on my 2.4 box running Apache-1.3.24. In fact, I used unset in almost every conceivable way without a problem. ------------------------------------------------------------------------ [2002-05-16 06:14:42] [EMAIL PROTECTED] No special script is required; even simple unset() calls fail: <?php $test = "test"; print "start"; unset($test); // hangs and finally fails due to timeout in this line ?> ------------------------------------------------------------------------ [2002-05-16 05:34:12] [EMAIL PROTECTED] Please provide a short reproducing script. Derick ------------------------------------------------------------------------ [2002-05-16 05:20:59] [EMAIL PROTECTED] My PHP 4.2.1 with Apache 1.3.24 has the following problem: unset() hangs in most cases in an infinite loop. It's independent from the type of the variable, or if the variable does exist at all. I experienced this problem only with the Apache-compiled-in version; the same PHP version as standalone CGI with the same compile options and php.ini doesn't have this problem. The apache process executing a script which came to an unset() call uses >90% of the CPU time until it gets stopped by the maximum execution time limit. register_globals is set to "On". ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=17268&edit=1
