I haven't seen this message yet. If you get it again, then please use kill 
-USR1 <pid> and check the stack trace.

I've changed #interCyclePause: recently, and I think the error can 
occur if you use the same WorldState object from multiple UI processes 
(but doing that is a bad idea).

Levente

On Thu, 12 Mar 2015, Chris Muller wrote:

> Has anyone else gotten the dreaded "This delay is already scheduled!"?
> The exclaimation suggests the author felt this should never happen;
> as a possible bug somewhere?
>
> I've gotten it a couple of times, this time I had interrupted
> something (taking longer than I thought?) and a flurry of debuggers
> with that message, but VM pegged at 100% and could not gain control of
> the image.  Had to kill -9 it.
>
>