Last time I checked, Ruby threads weren't "real" threads, i.e., it implements its own thread scheduler etc. So it may not even be using Win32 threading. While I have no idea if that was the cause of your thread starvation, its certainly the sort of thing that would make me think twice about using Ruby threads for serious threaded apps (esp I/O related, or anything else which needs to dive into the kernel).