#46950 [Opn->Fbk]: PHP 5.2.8 IIS ISAPI Crashing - Was Fine in 5.2.6

From: Date: Mon, 29 Dec 2008 11:06:56 +0000
Subject: #46950 [Opn->Fbk]: PHP 5.2.8 IIS ISAPI Crashing - Was Fine in 5.2.6
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-132378@lists.php.net to get a copy of this message
ID: 46950 Updated by: pajoye@php.net Reported By: w dot ashcroft at redfoxuk dot com -Status: Open +Status: Feedback Bug Type: Unknown/Other Function Operating System: Windows 2003 PHP Version: 5.2.8 New Comment: No, it does not, this is a very common place, called by almost every single script. But it will when we have a reproduce script. Previous Comments: ------------------------------------------------------------------------ [2008-12-29 03:41:53] w dot ashcroft at redfoxuk dot com Doesn't the backtrace provide any clues? ------------------------------------------------------------------------ [2008-12-28 12:20:02] pajoye@php.net FCGI works with IIS6 and IIS7, see http://www.iis.net/php Without a reproduce script, there is no chance to even have a diagnostic of your crash. ------------------------------------------------------------------------ [2008-12-28 11:09:49] w dot ashcroft at redfoxuk dot com I can't provide a script as the server is full of PHP based websites so the cause/trigger is unknown. Yes, but this particular server requires the ISAPI filter. ------------------------------------------------------------------------ [2008-12-27 10:11:55] pajoye@php.net We need a script as well. By the way, ever considered fastcgi instead of ISAPI? ------------------------------------------------------------------------ [2008-12-27 03:37:32] w dot ashcroft at redfoxuk dot com Made a mistake in the DebugDiag summary, it is actually: In w3wp.exe__PID__1652.dmp the assembly instruction at php5ts!zend_hash_del_key_or_index+10a in \\?\C:\PHP5\php\php5ts.dll from The PHP Group has caused an access violation exception (0xC0000005) when trying to write to memory location 0x0003213c on thread 0 ------------------------------------------------------------------------ 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/46950 -- Edit this bug report at http://bugs.php.net/?id=46950&edit=1

« previous php.bugs (#132378) next »