On Aug 17, 2010, at 2:05 11PM, TimM wrote:
Hi guys - it seems really easy to hang my seaside image and then have to force quit and restart. I thought that cmd-. was supposed to recover, but it never seems to work for me.
Am I doing something wrong? (I am using a pharo 1.1 seaside3.0rc3 image with the mac 4.2.5 vm).
I had the following code:
modelUpdate self pusher javascript: [ :jsScript | jsScript << (self generateUpdateScriptWith: jsScript) ]
generateUpdateScriptWith: jsScript
^aJScript goto: anActionUrl withoutQuery
I think that the << operator is adding something that has already been added via aJScript goto: - and so its recursive.
Anyway - when I hit this with my browser - the cpu of my Pharo image goes to 99% and I can hit Cmd-. all I want, but eventually it just dies - or I have to do a force quit.
Should it be so easy to kill an image like this?
Tim
Is this code run in a separate process? UserInterruptHandler>>handleUserInterrupt specifically interrupts the UI-process, rather than f.ex. the last process consuming cycles. Whether that is desired behaviour or not, is up for discussion :) Cheers, Henry