[Etoys] finalStripping hangs waitForCommand

K. K. Subramaniam subbukk at gmail.com
Mon Jun 15 22:06:42 EDT 2009

On Tuesday 16 June 2009 07:30:26 am David T. Lewis wrote:
> I have not tried this specific Etoys scenario but in general if an external
> process proxy does not go from #running to #complete, it is usually because
> that external process is still blocked while trying to write to its
> standard output or standard error stream, and thus is not yet able to exit.
In this case, no i/o was involved. The command (sleep 2) had indeed ended but 
the runState was not changed. I was able to get the code going by manually 
changing the state to #completed.

I suspect that the bug is related to specialObjectArray or VM changes but it 
just happened to affect waitForCommand:


More information about the Etoys mailing list