April 22, 2009
6:22 p.m.
Igor Stasenko wrote:
This is because all do-its executed in process, which responsible from handling UI events. To avoid 'hanging' you can just do like following: [ do what you need ] fork.
Oh, yes! Then i commanded a Full GC. I had to clean some 16 MByte Smalltalk stuff on my Notebook. 15 Seconds I had to wait, till my keystrokes and mouse events were accepted back again by Pharo GUI. Well, in the meantime, the seaside process was unresponsive. Ok, no real problem. Customers can wait and I have my coffee breaks ;-) World Wide Wait with Seaside Servers on Pharo ... Sorry, no access to The Salty Spitoon .... (not yet) ;-) Have fun, Guido Stepken