PHP CLI errors out under Windows 2008 / Vista when MapGuide extension loaded

[jbirch]

When running PHP in CLI mode, on exit Windows throws an error "CLI has stopped working". After commenting out the MapGuide API from the php.ini extensions, this error goes away.

How to replicate:

Create simple script called test.php:

<?php
phpinfo();
?>

From the commandline call:

php test.php

See error (image attached).

Comment out the PHP extension in php.ini and try again. Note the absense of error :)

This is important to address, as it makes it difficult/impossible to perform routine maintenance tasks through the command line in an automated fashion on these servers.

[jbirch]

MapGuide PHP CLI Error Message

[jbirch]

Found a workaround. This is not really an acceptable solution, but good enough to lower the priority of the ticket.

Add the following DWORD values to the registry:

HKLM\Software\Microsoft\Windows\Windows Error Reporting\DontShowUI = "1"

HKLM\Software\Microsoft\Windows\Windows Error Reporting\Disabled = "1"

Unfortunately, this entirely disables the WER UI and stops the reports from being sent to MS. Maybe not a problem on a dedicated server, but on a shared server often you want reports in things like MSSQL and ASP.Net sent to MS.

References:

​http://stackoverflow.com/questions/396369/how-do-i-disable-the-debug-close-application-dialog-on-windows-vista

​http://msdn.microsoft.com/en-us/library/bb513638(VS.85).aspx

[brucedechant]

This is a known PHP issue. PHP defect 38111 : PHP crashes IIS worker process and application pool

From the defect notes:

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.

Moving to FastCGI resolves this.

[jbirch]

I have a feeling that these are different bugs. This one is not ISAPI-related, and affects the command line interface version of PHP. Furthermore, it was only exhibited when the MapGuide extension was enabled.

[brucedechant]

Same issue. The error is caused by the way strings are handled internally within PHP. If we want to switch our extension to VC 2003/2005 and rebuild it this will work.

Problem is this would require us to rebuild our PHP extension and any of it's dependencies with VC 2003/2005 too. Maintaining this and the build for VC 2008 would be extra work.