[Seaside] VM freezes; how to find the cause?

Bob Arning arning315 at comcast.net
Mon May 27 14:00:32 UTC 2013

It may not be *that* hard. Start a high-priority process that frequently 
checks the state of Squeak memory and stops the offending process(es) if 
things are looking dire.


On 5/27/13 8:56 AM, Tobias Pape wrote:
> As Chris (?) figured out, your freeze was because of an infinite recursion,
> and those things are very hard to catch; it is actually no freeze but continuing
> execution. It is near impossible to catch that with the current architecture
> of either Squeak or Pharo.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20130527/12d8e637/attachment.htm

More information about the seaside mailing list