#16037 [Com]: random parse errors on dual xeon machine

ID: 16037 Comment by: fillmore@NRCan.gc.ca Reported By: hfielker@softsolutions.de Status: Critical Bug Type: Scripting Engine problem Operating System: Win PHP Version: 4.1.2 New Comment: We also ran into this problem. We found a workaround for the iPlanet/NSAPI environment which forces single- threading for PHP - it's documented in this bug report: http://bugs.php.net/bug.php?id=18869 - Bob Fillmore Previous Comments: ------------------------------------------------------------------------ [2002-07-22 21:16:55] mike@h3c.org I've got the same hardware setup as these guys (dual cpu win2k machine with lots of ram), and I still see this problem with PHP 4.2.2 right on up to the latest 4.2.2-dev stable snapshot (as of a few hours ago), so this is definitely still an issue. I haven't tried the workarounds yet, but others seem to find success so I just wanted to add another status report. ------------------------------------------------------------------------ [2002-07-10 04:29:22] estelle@megaphone.ch PHP 4.1.2 on a Solaris 8 box, Apache 1.3.26 : same problem. Random parse error (slashes around quotes not removed when doing a print("blabla \"blabla\""); when these quotes are coming from an array (nothing to do with stripslashes, this is a RANDOM error). This is critical for our clients. Especially for people who use softwares like php Nuke ... do you know the amount of changes in code that would be necessary to avoid the problem ?? But ... is there an answer from PHP or not ? ------------------------------------------------------------------------ [2002-06-07 16:48:10] agarza@campus.mty.itesm.mx I tried switching to PHP4.1.2 on Solaris 5.8, however the problems still remained. I followed the steps mentioned by chris@dvdplaza.com.au (editing the scripts), I was able to get the scripts to work--ALL STRINGS with ${variable} or $variable within them HAD to be changed to get rid of the errors. for example: echo "Hello $foobar"; $foo="This is a ${bar}"; changed to: echo "Hello ".$foobar; $foo="This is a ".${bar}; Don´t you think this is rather serious? (Random errors are a troublesome thing, arent they? Also, the lines reported as having errors were wrong most of the time). ------------------------------------------------------------------------ [2002-06-05 15:17:35] agarza@campus.mty.itesm.mx I am experiencing the same problem--random parse errors--on SunOS 5.8 with PHP 4.2.1. It seems the larger the script the easier it is to get a parse error. PHP is set up to run under NSAPI (Iplanet webserver). The setup is: './configure' '--with-mysql=/usr/local/www/biblio/dev/mysql' '--with-nsapi=/opt/iplanet/webserver/' '--enable-track-vars' '--enable-libgcc' ------------------------------------------------------------------------ [2002-05-09 18:00:52] chris@dvdplaza.com.au Been a week and a half and my error log is still dead silent since making those changes, compared with several MB worth of random/intermittent errors that occurred months ago when we first upgraded to PHP 4.1 onward. ------------------------------------------------------------------------ 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/16037 -- Edit this bug report at http://bugs.php.net/?id=16037&edit=1