Bob,
After much work (and some valuable assitance from Bob Arning) this weekend I was able to get my sim running without have Squeak become autistic (freezing up). This was accomplished by placing a Delay (1 second) between the #sendData: and #closeAndDestroy call on the socket.
BUT when I try the exact same code on 2.9a - it freezes.
Has anyone else seen this? Another engineer I work with has hung Squeak 2.9a by simply saving the image.
---John
PS> I'm running on Win2K (a 1GHz Athlon + 256MB RAM + 30G HD box); so is the other engineer.
jchludzinski@worldkey.net wrote:
BUT when I try the exact same code on 2.9a - it freezes.
Has anyone else seen this? Another engineer I work with has hung Squeak 2.9a by simply saving the image.
Have you tried forking the threads at a priority lower than the UI (i.e. use "forkAt: Processor userBackgroundPriority" instead of fork)?
This may tell you something.
A process running at or above the priority of the user interrupt handler can keep Squeak from responding to a user interrupt.
A process running below that, but at or above the priority of the UI, can keep you from being able to interact with the notifier that the interrupt handler brings up.
squeak-dev@lists.squeakfoundation.org