If you start clisp in a terminal and then kill the terminal window, sometimes there is a renegade "lisp.run" process that goes to 100% cpu usage.
Having a hard time reproducing, but the following has lead to the problem:
start a terminal
kill the terminal window with mouse
open another terminal
watch the zombie run at 100% cpu until you kill it...