ID: 16037 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Scripting Engine problem Operating System: Win PHP Version: 4.1.2 New Comment:
Well I've finally found the problem, having lived with all the hell this has caused all these months... Let's say you have a line such as: echo "$blah->blah!!!\n\n"; That line of code may work, but THAT is what is causing the random failures - if PHP 4.1 onward (including PHP 4.2) is used that line will randomly fail with parse errors. As a result of those parse errors, the scripts would not have been fully loaded into memory and what ends up executing causes even more errors. I have edited such references in a third-party script we purchased to instead read as follows: echo $blah->blah . "!!!\n\n"; As a result of this, instead of my error log filling up thick and fast per MINUTE with all these weird parse errors (and as a result 90% or so of page requests working, the remainder failing with a blank page or partial page) the error log has been dead silent this past couple of hours and I've not yet seen a single page failure! Previous Comments: ------------------------------------------------------------------------ [2002-04-30 22:26:04] [EMAIL PROTECTED] We have EXACTLY the same problem, and it is 100% specific to PHP 4.1 onward (ie both PHP 4.1 and now PHP 4.2 do this). For example sake let's compare 4.0.6 to 4.2 - install PHP 4.2 and everything works fine, but every so often (let's say 10% of the time) they get nothing/part of a page and the error log shows a parse error (whinges about all sorts of stuff that isn't true) - a simple refresh solves this problem. It's easily reproducable, though as per the original repor there it might be load related as we get a lot of activity. Now here's the thing - PHP 4.1 introduced this, if you put PHP 4.0.6 back on everything is 100% PERFECT. Put 4.1 or 4.2 back on and 10% or so of requests fail, put 4.0.6 back on and it's perfect, put 4.1 or 4.2 back on and the problem is back - this has been major hell for us and I hoped to heck 4.2 would fix it, but alas the problem still exists.... HELP!!!! Running as a module under Apache, was Apache 1.3.24 until last night - as of last night we're now under Apache 2.0.35, with the same problem. ------------------------------------------------------------------------ [2002-03-13 06:28:26] [EMAIL PROTECTED] I am using Php in a Win enviornment. The machine has a Raid 5 system, 1GB Ram and two Xeon 700 CPUs. PHP runs in Apache (1.3.23) as Module. I am using "official" binaries PHP and Apache. There are very strang parse errors in files that are 100% ok. The files are used in three other installations and there are no errors at all. I think there is something bad with threading. I noticed the error when a session is accessed within a frame e.g. 3 or more independant PHP files usind the same data. There is a newsgroup posting dealing with the same problem: http://groups.google.com/groups?q=php+xeon+parse+error&hl=de&selm=Pine.BSF.4.10.10203070837300.22588-100000%40sea-incorporated.com&rnum=1 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=16037&edit=1
