On Fri, 12 Jun 2009 07:19:40 -0400, "David T. Lewis" lewis@mail.msen.com wrote:
It does not sound like you are missing anything. Are you encountering problems with this, or are you just asking to be sure?
Actually, it appears that the problem is in a different place.
After starting the CPUWatcher in the process browser, the hangup appears to happen inside the Socket code, on a server socket.
I call Socket >> #receiveDataInto:startingAt: and after a while, CPUWatcher complains that that process is taking too much CPU. Note that I'm running on an older system (3.8, Update #6665), with the 3.10.6 (release) VM from Aug 30, 2007 (on Windows XP).
There's no reason why I can't move forward to 3.10.2, so I will try that, and hopefully whatever this issue is has been fixed -------------------------------------------------------------- Jon Hylands Jon@huv.com http://www.huv.com/jon
Project: Micro Raptor (Small Biped Velociraptor Robot) http://www.huv.com/blog