Sequence of events: 1. Camino (1.6.1 + trunk) hangs. User force quit: Cmd-Opt-esc or via Activity monitor. The process is killed (?) - the users sees the browser vanish. 2. User looks at the Dock: Camino is apparently still running: the spot-light-reflection thingie under the dock-icon is still there. 3. Activity Monitor does _not_ report a Camino instance as running. 'Top' does not see Camino as running. But Command-tab shows Camino as active (but you can't bring it up). Right-click on Dock icon says 'application not responding', but a second Cmd-Opt-click does nothing. 4. Click on Dock icon, or on Camino.app in Application folder to start it up: a warning pops up: 'The operation could not be completed. An unexpected error occurred (error code -600).' 5. The user logs out and logs back in. Seemingly normal operation can resume. I say seemingly, because the other day, I then found this in the logs: 6/2/08 9:18:48 PM com.apple.launchd[159] ([0x0-0x1eb1eb].org.mozilla.camino[18569]) Did not die after sending SIGKILL 32270 seconds ago... Repeated every 5 seconds. The PID (18569) matched the one for the Camino that enjoyed the hang 6. The only way I found to restore a normal behaviour: Shut down (or more exactly force shut down) the machine. A normal shut down would kinda hang during logout (all windows would close, Dock hidden, menu bar gone), but you are left facing a spinning progress meter - not the beachball. The first time it happened, I let it run for ~10min before losing patience. This _may_ be unrelated, there is a longish thread on the Apple forums on a similar problem: http://discussions.apple.com/thread.jspa?threadID=1540494&tstart=0 I must note, however, that both machines shut down normally otherwise. I have reproduced this 3 times: * with Camino 1.6.1 running under Troubleshoot Camino - at startup, I think. * with Camino 1.6.1 (on another machine, where it is the default browser): hang at start up. * with my home-made Camino trunk build (hang while doing a search on Bugzilla, sample of that hang attached). Console logs don't reveal anything at all. All 3 cases: OS is 10.5.3, running on Intel C2D iMacs.

Pretty sure this is the same issue as bug 436575. That would make this an Apple bug. (And that bug should really move to Core.)

Right, pretty similar, I think. Based on that and my report above, I've submitted a Bug Report @ Apple: Bug ID# 5987623.

On the bright side, that means that these unkillable hangs I've been getting inside of filesystem calls since upgrading to 10.5.3 probably aren't due to something terribly wrong with my machine.

Pretty sure this is all platforms, as I just saw this same thing yesterday.

Has anyone tried (re)applying the Combo updater? My understanding was that that bit of troubleshooting voodoo was related to the bug Apple fixed by forcing updates to install with no user processes, but it's worth a shot :P Let's dupe this, and if for some bizarre reason they don't end up being the same, we can pull it back apart.