Edit report at http://bugs.php.net/bug.php?id=38111&edit=1
ID: 38111 Comment by: santafe05-blog at yahoo dot com Reported by: svendavidh at hotmail dot com Summary: PHP crashes IIS worker process and application pool Status: Bogus Type: Bug Package: IIS related Operating System: Windows Server 2003 Std. Ed. R2 PHP Version: 5.2.8 Assigned To: pajoye Block user comment: N New Comment: I recently installed PHP on Vista. I'm new to Open Source stuff and so after seeing the dates on this I was/am literally shocked to see this same bug that is experienced by so many people (A) stay in place for years, and (B) be judged as 'bogus'. And there are many other identical threads reporting the SAME problem. http://bugs.php.net/bug.php?id=44047 forums.techarena.in/showthread.php?t=686723 www.developersdex.com/asp/message.asp?p=592&r=6057007 www.issociate.de/board/post/468636/IIS_+_PHP_--_Worker_Process_alert_&_w3wp.exe_crash?.html forums.techarena.in/showthread.php?t=821723 groups.google.com/group/comp.lang.php/browse_thread/thread/93aef1ff2f0ba3b0 www.thescripts.com/forum/thread742344.html Previous Comments: ------------------------------------------------------------------------ [2009-03-04 20:05:00] paj...@php.net For the 100th time, never use mysql 5.1 DLL with PHP. Closing this bug as well as no useful information has been provided and the ISAPI is going to be deprecated anyway. Use FastCGI istead with IIS5/6/7. ------------------------------------------------------------------------ [2009-03-04 18:46:44] info at cmiwebstudio dot com PHP 5.2.9 IIS 6 WIN Server 2003 Standard MySQL 5.1.31 Same problem indicating a problem with php_mbstring.dll . Also getting "Invalid access to memory location." on PHP pages. ------------------------------------------------------------------------ [2009-02-19 04:59:39] sikle at stx dot net i've resorted to just using apache (via xampp) instead... hrmph. but atleast now it doesn't crash =) ------------------------------------------------------------------------ [2009-02-18 01:00:01] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, 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". ------------------------------------------------------------------------ [2009-02-10 21:50:51] paj...@php.net Yes, a simple phpinfo and then restart IIS is all it need to crash. (Note: I am using IIS on Vista 64, and have to create a new Application Pool and then enable 32-bit application) As for why we stick with ISAPI: "1. We have an php extension for handling proprietary protocol and it has significant overhead on startup. We will try FastCGI, but in the meantime we keep in in ISAPI mode so that it won't get loaded and unloaded frequently." That should not be a problem at all. "2. FastCGI could be way better, but ISAPI is still a legitimate mode for PHP. So I am a bit surprise to see you persuade others to use FastCGI as a way to avoid this bug. Well of course, use Apache or Linux also "fix" this problem as well." Nobody maintains it and it is likely to be dropped. It was never stable and it is very unlikely that we will fix it any time soon. It is also the recommend way, according to the IIS team (and I work with them on that). "BTW, FastCGI is an excellent idea to make PHP more stable. But I am worry it becomes a way to hide all the thread-safe, memory leak issues and allow them not being fixed properly." There is no tread safety issue with fastcgi because this SAPI is not threaded (like ISAPI or some apache2 sapi). I do not understand your point with the memory leaks. ------------------------------------------------------------------------ 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/bug.php?id=38111 -- Edit this bug report at http://bugs.php.net/bug.php?id=38111&edit=1
