Re: [Chicken-users] Spiffy subprocess cleanup

[Evan Hanson]

After looking at a bit more, here's what I believe is *actually*
happening:

The invalid call to process* is signaling an exception in the child,
which is handled internally by spiffy (spiffy.scm:470), causing that
process to loop back to the start of the accept-next-connection
procedure inside spiffy's accept-loop. At this point you have two
processes listening on 8080, with the parent waiting for the child (who
has no plans to exit). The same thing happens with each request, so the
subprocesses pile up.

Evan