ID: 21319
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: No Feedback
Bug Type: Scripting Engine problem
Operating System: windows xp
PHP Version: 4.3.0
New Comment:
Hello, I've run into what seems to be the same problem.
I also have a way to reproduce it:
WinXP HE (NT 5.1), Apache 1.3.27, PHP 4.3.0 on CGI-FCGI
?php
error_reporting(E_ALL ^ E_WARNING);
set_time_limit(10);
for($x=1;$x1;$x++){
$f = fsockopen('127.0.0.1',$x,$errno,$errstr,1);
print Port $x: ;
print($f)?'Success!':'Failed!';
print br /;
}
?
Almost every single time it causes an HTTP 500 Error
This from the server's log:
[Sat Jan 25 01:00:23 2003] [error] [client 127.0.0.1] Premature end of
script headers: {PATH TO PHP}/php.exe
[Sat Jan 25 01:00:23 2003] [error] [client 127.0.0.1] FATAL:
erealloc(): Unable to allocate 10 bytes
You may need to refresh that page a few times to get the Program has
crashed and needs to close/Report to MS window. When this happens, the
browser hangs until you click something on that dialog box.
btw, I've also increased the timeout to fsockopen(), while the error
still occures, it seems easier to reproduce with lower timeouts.
I have the files appcompat.txt, manifest.txt and php.exe.mdmp generated
by the error reporting app available upon request.
Could this also be related to http://bugs.php.net/bug.php?id=21262 ?
Thank you for your time.
- Alex, http://alexnow.com
Previous Comments:
[2003-01-24 01:00:02] [EMAIL PROTECTED]
No feedback was provided for this bug for over 2 weeks, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to Open.
[2003-01-08 13:34:41] [EMAIL PROTECTED]
Hi,
sorry I haven't been able to isolate in sort, but I found out this much
:
Installing 4.3.0 by default enables the php_iisfunc.dll extension in
the php.ini file. (Using Windows XP and IIS).
I'm not aware of using this functionality and when I remove the use of
the php_iisfunc.dll (comment the line) the error doen't occur.
Hopefully this can be of some use.
/Rene'
[2003-01-08 13:27:31] [EMAIL PROTECTED]
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.
[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
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=21319edit=1
