After\ Dark strangeness

[Damon Permezel]

When I am running the desktop stuff, and After\ Dark is installed, I have
observed that there are some pixels in the top left corner, which, if I move
the cursor into, will cause After\ Dark to draw a few lines of screen
saver stuff, pause for 1sec - delta, draw .... and so on.
Moving the mouse slightly will cause After\ Dark to function normally,
which is to say it gets all the CPU it needs.  This is when the system
is otherwise quiescent.  I cannot get it to perform similarly when
just booted up on the MacOS with the same inits installed (no surprise here). 

This is what the system is doing when I get the parkinsonian behavior:
(three successive snapshots, sorted and merged)
   F S   UID   PID  PPID  C PRI NI     ADDR  SZ    WCHAN TTY      TIME COMD
4410 S     0   265   264  0   0  0   5770006329 12013a88 console  2:09 startmac
4410 S     0   265   264  0   0  0   5770006329 12013a88 console  2:09 startmac
4410 S     0   265   264  4   0  0   5770006329 12013a88 console  2:09 startmac
4410 S     0   266   264  2   0  0   5bc0006457 12002458 console  5:07 CommandS
4410 S     0   266   264  2   0  0   5bc0006457 12002458 console  5:07 CommandS
4410 S     0   266   264  4   0  0   5bc0006457 12002458 console  5:07 CommandS

This is what it thinks is going on when it is running smoothly:
(three successive snapshots, sorted and merged)
   F S   UID   PID  PPID  C PRI NI     ADDR  SZ    WCHAN TTY      TIME COMD
4410 S     0   265   264  0   0  0   5770006329 12013a88 console  2:09 startmac
4410 S     0   265   264  0   0  0   5770006329 12013a88 console  2:10 startmac
4410 S     0   265   264  1   0  0   5770006329 12013a88 console  2:10 startmac
5410 R     0   266   264 40  60  0   5bc0006457          console  5:22 CommandS
5410 R     0   266   264 69  74  0   5bc0006457          console  5:33 CommandS
5410 R     0   266   264 68  73  0   5bc0006457          console  5:44 CommandS

Observations:
	12002458 is `selwait', which implies that if the mouse is a certain
place on the screen, CommandShell is sitting in a select loop with a 1 second
timeout, and therefor not running any threads associated with it's menu bar.
Is this correct?  Does this mean that one should avoid leaving the pointer at
certain screen locations?