Sounds like exhaustion of some OS network-related resource, that is then released when the process exits. This is reinforced by your observation that regular restarts of the process remove the problem. Naively I'd suggest monitoring the handle count for the Squeak process as a first step, but Andreas probably has some much better ideas for monitoring!
- Peter
Looking at the handle count, I'm seeing a fresh image start with around 40 or so, and an image that's been up a bit, pushing 5000, much more than any other process on the box. I'm still waiting for another crash, but this seems a likely suspect, any more ideas?