[Seaside] problem restarting servers when VM comes up

[Jake Donham]

Hi,

Using Seaside 0.92 with Squeak 3.0 and Comanche 4.10 on a Redhat Linux 
6.2 system, if you save and quit while a server is up, the VM crashes:

Segmentation fault

1085305112 SystemDictionary>snapshot:andQuit:embedded:
1085305020 SystemDictionary>snapshot:andQuit:
1085304744 TheWorldMenu>saveAndQuit
1085304836 [] in TheWorldMenu>doMenuItem:with:
1085304652 BlockContext>on:do:
1085304008 TheWorldMenu>doMenuItem:with:
1085303640 [] in MenuItemMorph>invokeWithEvent:
1085303916 BlockContext>on:do:
1085304376 [] in BlockContext>valueUninterruptably
1085303824 BlockContext>on:do:
1085304192 [] in BlockContext>valueUninterruptably
1085303732 BlockContext>on:do:
1085303548 BlockContext>valueUninterruptably
1085303456 BlockContext>ensure:
1085303364 Cursor>showWhile:
1085303140 MenuItemMorph>invokeWithEvent:

I tried Squeak 3.2 gamma, and while it doesn't crash on exit, when I
restart it, the server is not running. However, as far as I can tell
from poking around in ComancheServer, it is still registered in
Comanche's list of active servers, so if you try to start it or set it
to auto-start, Comanche complains that there's already a server on
that port.

This seems like a Comanche problem rather than a Seaside problem but I
though I might find a friendly ear on this list. If there's somewhere
else I should ask please let me know.

Thanks,

Jake