View Single Post
Sorry, this appears to be caused by a Leopard bug that only happens on PowerPC hardware. (As far as I can tell it never happens on Tiger or on Intel hardware.) Basically, what happens is that we create a child process and wait for it to exit, but somehow the exit notification gets lost and we end up waiting forever.

We're trying to come up with an alternate approach that works around this bug. Sorry for the inconvenience in the meantime!