ID: 21319
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Feedback
Bug Type: Scripting Engine problem
Operating System: windows xp
PHP Version: 4.3.0
New Comment:
Don't quote me on this, but I believe this bug is related to several
other bugs which have been reported since 4.3.0.
There *appears* to be an issue with garbage collection when the
interpreter is in the final stages of shutdown (script exit).
I can't be more specific because it's related to a portion of the PHP
Core which I'm not qualified to debug and is a heisenbug in the most
classical sense.
Rest assured though that there ARE developers working on this issue.
Any additional information you can provide such as backtraces and
short, simple pieces of code which reproduce the error will aid in the
isolation and irradication of this bug.
Previous Comments:
------------------------------------------------------------------------
[2003-01-07 17:46:07] [EMAIL PROTECTED]
In order to look into the problem we would need a short and complete
script that reproduces the problem. Without that there is very little
information to go on.
------------------------------------------------------------------------
[2003-01-07 14:05:53] [EMAIL PROTECTED]
i withdraw my speculation about the die construct beeing the problem;
i have a script that does.. something (checks urls & downloads them via
fsockopen) 20 times in a for loop from 1 to 20.. sometimes there is an
error when downloading, and naturally, to move on to the next url, i
use the continue construct (or whatever it's called).
I run my scripts from the command prompt with a batch script that runs
"PHP SCRIPTNAME.PHP" over and over in an infinite loop..
since the php script is executed in a loop, it wouldn't really matter
if you call continue or die since the next url in the database would be
processed either way..
Now this should be interesting;
NOT A SINGLE CRASH, has ever occurred ever since i've started using die
instead of continue on download errors..
and you're still not responding..
osman darcan
------------------------------------------------------------------------
[2003-01-07 13:56:48] [EMAIL PROTECTED]
I am using Apache and yes, it may be the same problem, what i don't
understand is why these guys dont respond, i would really like to know
if they're into the problem or if they haven't even read my messages
yet..
a simple "we're looking into the problem" would be fine.. but nooo..
------------------------------------------------------------------------
[2003-01-07 03:19:18] [EMAIL PROTECTED]
Hi, i'm getting the same errors on two different Windows XP Pro
installations.
I'll try to get some more information (xp related addresses from the
crash) but from the head i remember that the problem is
php_iisfunc.dll.
The web'server (PWS) serves seems the pages correctly but at the end of
the session the error occurs. I can reproduce the error everytime in
multiple scenarios.
I know there is another reported bug related to Apache under WinXP
(php_apachefunc.dll) and i won't be surprised if this is actually a
related issue.
------------------------------------------------------------------------
[2003-01-04 05:08:38] [EMAIL PROTECTED]
Hi, i've just upgraded to php 4.3.0 and i'm pleased the fsockopen
timeout problem has been fixed..
but now to something more serious:
the php script interpreter crashes, windows takes over command and
says
"PHP Script Interpreter has encountered a problem and needs to close.
We
are sorry for the inconvenience." and you get to choose to send or
dont
send an error report to microsoft
("please tell microsoft about this problem" it says)
this happens very often... i suspect this has something to do with the
die() construct and/or the mysql interface... because the crash often
comes directly after a erroneus mysql query a it's
die-error-message...
but not always.. i think.. sometimes no error is produced by php at
all..
i want to be of more help by telling you how to reproduce the error
but
i haven't figured out how to figure out how to tell you to reproduce
the
error..
------------------------------------------------------------------------
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/21319
--
Edit this bug report at http://bugs.php.net/?id=21319&edit=1
