Able to hang the Squeak UI

> Regards
>
> Charles
> P.S.  The Seaside framework is truly awesome and to-date a fairly well
> kept secret but that will change. Kudos to Avi and the rest.
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> When I am debugging a Seaside app using the browser, I am often able to
> hang the Squeak UI; my mouse works, the app will still run using the
> browser but I am unable to regain control of the Squeak image,
> consequently I have to exit Squeak and restart.  I would appreciate your
> help.
>
> Regards
>
> Charles
> P.S.  The Seaside framework is truly awesome and to-date a fairly well
> kept secret but that will change. Kudos to Avi and the rest.
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> -----Original Message-----
> From: [hidden email] [mailto:seaside-
> [hidden email]] On Behalf Of Lukas Renggli
> Sent: Tuesday, July 03, 2007 3:23 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Able to hang the Squeak UI
>
> > It's a common problem. I can't help you now but you can save your access
> > and regain a usable image by using the screenshot application
> > WAScreenshot in the tools section with a web browser. Here you can
> > restart the suspended UI display by clicking on 'Resume UI Process'.
>
> I fixed this very problem this afternoon. Load the latest version of
> Seaside 2.8a1.
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> > What did you find?  What did you fix?
>
> The variable semaphore in WAProcessMonitor>>#critical:ifError: has to
> be an instance-variable, even so it is only used within this method.
>
> This was changed some time ago, as it seemed to be more natural to
> make it a temp-var. However this introduced a subtle regression with
> continuations causing the lock not to be released in some situations
> with the debugger. The issue is now documented in the method itself
> and should not occur anymore!

> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> > What did you find?  What did you fix?
>
> The variable semaphore in WAProcessMonitor>>#critical:ifError: has to
> be an instance-variable, even so it is only used within this method.
>
> This was changed some time ago, as it seemed to be more natural to
> make it a temp-var. However this introduced a subtle regression with
> continuations causing the lock not to be released in some situations
> with the debugger. The issue is now documented in the method itself
> and should not occur anymore!
>
> Lukas
>

> -----Original Message-----
> From: Lukas Renggli [mailto:[hidden email]]
> Sent: Tuesday, July 03, 2007 4:01 PM
> To: [hidden email]; Seaside - general discussion
> Subject: Re: [Seaside] Able to hang the Squeak UI
>
> > What did you find?  What did you fix?
>
> The variable semaphore in WAProcessMonitor>>#critical:ifError: has to
> be an instance-variable, even so it is only used within this method.
>
> This was changed some time ago, as it seemed to be more natural to
> make it a temp-var. However this introduced a subtle regression with
> continuations causing the lock not to be released in some situations
> with the debugger. The issue is now documented in the method itself
> and should not occur anymore!
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch