User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.14) Gecko/20080512 Camino/1.6.1 (like Firefox/2.0.0.14) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.14) Gecko/20080512 Camino/1.6.1 (like Firefox/2.0.0.14) Camino went into an unresponsive state and had to be force quit. After this it would not relaunch, reporting an error -600 from the app, and not doing anything from the dock. Safari and Firefox would go unresponsive on launch and also need to be force quit. Logging out and back in did NOT resolve this, Camino then reported it was already running, but it did not show up in the process list. Apparently Camino somehow locked up and crashed a core component required for any web browser, and was running something as root since user processes are terminated at logout but it was not. This is all very bad. Reproducible: Couldn't Reproduce Steps to Reproduce: I could not reproduce this once the system was rebooted to repair the problem. Apparently it was a random failure, but it points to some very bad behavior.

Are you running Mac OS X 10.5.3? If so, this is a known bug in Mac OS X 10.5.3 (bug 436575).

(In reply to comment #0) > Camino then reported it was already running, but it did not show up in the > process list. Apparently Camino somehow locked up and crashed a core component > required for any web browser, and was running something as root since user > processes are terminated at logout but it was not. Unless you ran Camino as root, it wasn't running as root. If this was bug 436575 (which it almost certainly was), what you were seeing was an unkillable zombie process due to a serious bug in Apple's dynamic linker/loader.

Absent any other explanation, I'm duping this.