Comment 3 for bug 772471

I have this exact same problem using the win32-x86 EPICS base port as a bridge to transfer process variables from WinXP to linux.
A python script is run on the linux box that does a caget once a second to retrieve a flag. When the flag is in a certain state, the script does ~80 cagets to grab a bunch of process variable. Attached shows the handle count (on WinXP using Perfmon.exe) while the script is running. When the script is killed, the handle count flatlines but does not decrease.
If the script is run long enough, it will:
1. start giving a winxock error 10055
2. eventually cause a system crash on winXP (blue screen) as the machine eventually runs out of system resources.
I've tried this a couple of times, and both happened without fail each time.

I initially thought this was a tcp socket that's not being closed at the end of a call, but netstat -a does not show any tcp connections accumulating.