Hi, It seems that the problem is fixed. Not sure why Pharo image went freeze because it was a Seaside problem. (maybe i should execute the same on GemStone/S to see the result). Also not sure why Control + "-" did not halt the execution. Even in one occasion make Windows 8 fail. The problem was the reuse of already created components in as argument of call. editComponent := WAEditComponent new. self call: editComponent. This inst var was store in a parent and at some point instead of creating a new component for the call we call again: self call: editComponent. After changing all call to a new fresh WAEditComponent the problem was fixed. It seems that Seaside went into a infinite rendering loop (after all :) because the already instantiated element. Any thought about this is welcome because i did not totally close this issue :) regards, bruno -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html