#21319 [Sus->Opn]: the PHP Script Interpreter crashes.

ID: 21319 Updated by: sniper@php.net Reported By: odarcan@hotmail.com -Status: Suspended +Status: Open Bug Type: Scripting Engine problem Operating System: windows xp PHP Version: 4.3.0 Previous Comments: ------------------------------------------------------------------------ [2003-01-04 05:08:38] odarcan@hotmail.com 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.. ------------------------------------------------------------------------ [2003-01-02 15:52:59] odarcan@hotmail.com i have by the way only 500 MB of ram ------------------------------------------------------------------------ [2003-01-02 15:51:55] odarcan@hotmail.com FATAL: emalloc(): Unable to allocate 1936028514 bytes is this php's fault or the os'? ------------------------------------------------------------------------ [2003-01-02 15:24:33] odarcan@hotmail.com "this just in": FATAL: erealloc(): Unable to allocate 59 bytes and then again: BOOM cool eh? ------------------------------------------------------------------------ [2003-01-02 11:51:16] odarcan@hotmail.com I AM STILL WAITING FOR YOUR COMMENTS WAKE UP PLEASE ------------------------------------------------------------------------ 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