How can process in STOP state consume 200% CPU?

[perryh at pluto.rain.com]

Yuri <yuri at rawbw.com> wrote:

> kill -9 doesn't kill it.

I think I've seen this before; it looks as if, since the process is
STOPped, the "kill -9" remains pending rather than being acted upon.
I _think_ you can make the process go away by doing a "kill -CONT"
after the "kill -9".

No idea how a STOPped process can continue to consume CPU, unless
in an infinite loop at elevated interupt level (and in that case
the "kill -CONT" may not work -- you may need to drop into kdb, try
to do some debugging and/or get a dump, and then reboot).