[John Rogers]

It's a server issue:

"You should also understand that errors and troubleshooting are very different with FastCGI vs. regular CGI. If a FastCGI script has an error, a web page with a bad script will try to load for a few minutes rather than failing immediately, looking like a hung page. Also, if you fix the error, and try to reload the page, the server will still try to execute the old version of the script rather than the new one, so the page will continue to stall when loading. You solve this problem by killing the FastCGI process to force the server to load the newest version of the script."