site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com You need to: (1) make sure you have two extra Terminal windows open (2) do NOT set Terminal windows to close on process exit (3) cause the problem while the extra windows are open (4) after the problem happens, issue the command: exec ps gaxlwww -- Terry Hello , on both powerpc-apple-darwin9 and i686-apple-darwin9 nothing will launch from the dock, double clicking ... or open -a. log out / back in solves the problem. cheers, Iain _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/tlambert%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Your process table is full. The most likely cause is the dejagnu test suite not reaping its zombie child processes. Other possibilities are you are running the older buggy dejagnu test suite which closes the master side of the pry before the child process has drained its output, so the individual tests are stuck waiting for someone to reopen it and read their output so their closes can complete, or you have some other runaway software, or you have software that calls out to userspace from a kernel next and deadlocks itself when it makes a system call because it did not make itself immune to its own outcalls (usually firewall or antivirus software). In the first extra terminal window. This will replace the shell, but tell you about the processes (which you will be able to scroll back to because of #2) (5) look at who the parent process is for all the zombies. If there are no zombies, you should be able to identify a forkbomb by process name. Otherwise look for third party software to reinstall to see if you can resolve a deadlock. (6) in the second extra terminal window, shoot that process in the head (if it's a forkbomb type runaway, you can exec the kill command to use the shell process slot to do the kill in the second window; you will lose the shell but you should be able to open new windows after that, if you killed the right thing) (7) never, ever, run that process again, unless you have fixed it to reap its children correctly/not run away, and recompiled and reinstalled it On Sep 5, 2009, at 1:51 AM, IainS <developer@sandoe-acoustics.co.uk> wrote: I have a phenomenon I'm trying to understand. I run a large dejagnu testsuite (the gcc make check) from time to time and some amazing interaction has appeared. almost (>90%) on every occasion I run the testsuite it trashes application launch. The error message reported is [alert dialogue] "the application xxxx cannot be launched. -10810" neither google nor support on the apple website have proved illuminating on what the error message means .. and I'd like some opinions on how to debug this interaction. This email sent to tlambert@apple.com This email sent to site_archiver@lists.apple.com