Apache stops in Vista

[dkeays]

Starting today every time I start XAMPP with the .BAT file, within 3 minutes or I get a message from Windows saying there was an error.

I get the following event in the log:
"Faulting application apache.exe, version 2.2.9.0, time stamp 0x4853f994, faulting module php_xdebug.dll, version 2.0.3.0, time stamp 0x47fcd9b9, exception code 0xc0000005, fault offset 0x00008493, process id 0xcc0, application start time 0x01cab568ba7f8606. "

I started using XAMPP several years ago and the only recent change was done several days ago (getting the XDEBUG server installed).

UPDATE 2/24 14:20:00 : I removed/commented the lines for XDEBUG in PHP.INI No changes

[dkeays]

Ok, so deactivating XDEBUG and then restarting the Windows user did the job. I'll be trying newer releases of XDEBUG in the next day or two.
UPDATED, 2-28-2010 SEE POST BELOW

[dkeays]

It came back. checking the Apache error log (apparently I didn't do what I thought I did) it shows:
[notice] Parent: child process exited with status 255 -- Restarting.

BTW: It would be nice if the BB code [S] (strikethrough) was allowed

[dkeays]

Ok, my last posting (I hope) on this thread. Four things I've learned:

1- Using the XDebug server in my PHP seemed to aggravate the situation, but removing it didn't help 100%.

2- Same with an old Visual Studio 6. The error messages were mentioning VS6's debugger, but removing it wasn't a 100% solution.

3- If Textpad is set to insert a UNICODE signature (BOM) then my dev system blew up every time I used a PHP file I edited with Textpad. I changed this because of WSODs (white screens of death) in Drupal but after changing it the problem with Apache stopping went away for new edits. They still exist for files I edited, but item #4 below solved that problem.

4- To recover a file I previously altered with BOM enabled Textpad I needed to cut the content and paste it into a new file using an editor that didn't add the BOM.

I hope this helps someone.