Socket>>#waitForDataFor:ifClosed:ifTimedOut: large delay hangs process

squeakdev1 at squeakdev1 at
Mon Jan 14 15:55:28 UTC 2008

On rare occasions I've seen
Socket>>#waitForDataFor:ifClosed:ifTimedOut: (3.9 svp 7/27/2003 00:16)
pass a very large duration to readSemaphore waitTimeoutMSecs:. Large
enough to either hang the process for days, or cause Delay to complain
that delays cant exceed ~6 days. (when the duration should have been a
max of  300 seconds).

Is it possible that there is a problem in this code when the
millisecondClockValue is reset or rolls over? I'm was wondering if
totalSeconds could be used instead of milliseconds to avoid roll
overs, or is seconds too coarse to be used here?

More information about the Squeak-dev mailing list