you sir are an idiot.
unless you post code that can recreate the problem and demonstrate a bug with php, no one really cares.
if you want to talk about unreliable and crap scripting languages, lets talk about ASP & COM components. Reboots on a regular basis are fun. Keeping a user logged onto the server (but the screen locked) so that ASP & MS SQL format dates in the right format is fun (date formats are user specific. no logged on user = default date format). Forget to have a user logged on or have someone else logged on means scripts fail to run. Having COM components suddenly stop responding to MTS until a system reboot is fun. ASP scripts that fail to run for no obvious reason when under a different site in IIS is the highlight of my day.
so now that i've gotten that out of my system:
1) Post the minimal amount of code necessary to recreate the issue. We here have an extremely short attention span.
2) When troubleshooting ANYTHING assume you screwed up somewhere first, and ask your self what did you change.
3) If it works somewhere else and no one can find fault with the code then its likely a software corruption issue. Completely reinstall PHP.
4) If it still fails, only then you might have a bug. Upgrade PHP.
I've got boxes running LAMP (Linux, Apache, MySQL, PHP) with uptimes exceeding a year with 0 problems with Apache/MySQL/PHP. Don't blame a tool (and a free one at that) that you don't know how to use.