2007/9/1, Janko Mivšek <
[hidden email]>:
> Hi Philippe,
>
> Philippe Marschall wrote:
>
> > I'm currently working on a sever adapter for Swazoo 2 and encountered
> > the following issue:
> >
> > If I don't stop the swazoo server before saving and quitting the
> > Squeak Image the next time I start the image it will constantly use
> > 100% CPU. This migh occur if you don't check if the Socket is still
> > valid (could be a Sport issue).
>
> I have the same problem with Squeak Aida but so far I didn't yet start
> to dig into. I also don't have enough Squeak experience and I'd really
> appreciate some help here.
>
> But you could see a culpit process in Processes inspector and kill it.
> To debug it instead is maybe a way to go? Also, does Swazoo need to do
> some socket cleanup before image shutdown?
SpEnvironment class >> #addImageShutdownTask:for:
is not implemented in Squeak :-/
Cheers
Philippe
> Best regards
> Janko
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>
http://get.splunk.com/> _______________________________________________
> Swazoo-devel mailing list
>
[hidden email]
>
https://lists.sourceforge.net/lists/listinfo/swazoo-devel>