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

Bahman Movaqar Bahman at BahmanM.com
Mon May 27 14:03:56 UTC 2013

On 2013-05-27 18:30, Bob Arning wrote:
> 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.

@Bob: You mean an OS-level process or Squeak-level?

> Cheers,
> Bob
> 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.

@Tobias: That's not good.  Imagine an image serving multiple sites.  If
one site gets blocked, all other will be unresponsive as well :-(

Bahman Movaqar  (http://BahmanM.com)
ERP Evaluation, Implementation, Deployment Consultant

More information about the seaside mailing list