ADB execution hangs in "adb fork-server server"

[bdb]

Hi All,

I'm working on a tool that provides android test automation
capabilities over the adb interface. I'm seeing an issues sometimes
where the adb process will hang waiting for a sub-process to complete,
the sub process command line is "adb fork-server server". I've been
able to reproduce this manually by launching "adb fork-server server"
numerous times via the command line. After about 10 iterations of
this, you can see the process hang in the exit() system call. I've
only been able to reproduce this on Microsoft Windows XP based PCs.
So, i'm thinking this might be a windows specific issue. I've attached
some debug information I was able to gather:

Stack Traces of ADB Hanging in "adb fork-server server" call

1) // This is the stack trace from a hung adb call running on a live
system
0022c63c 7c901046 0197e178 7c914a53 7c97e178 ntdll!KiFastSystemCallRet
0022c680 7c9168f0 00000000 00000000 0022c6c4 ntdll!
RtlEnterCriticalSection+0x46
0022c6f4 7c9166b8 00000001 00000001 00000000 ntdll!LdrGetDllHandleEx
+0x22f
0022c710 7c80e534 00000001 00000000 0022c794 ntdll!LdrGetDllHandle
+0x18
0022c760 7c80e64b 0022c794 0041d6cb 00000001 kernel32!GetModuleHandleW
+0x57
0022cbe4 7c80e4fc 00000001 00000002 7ffdec00 kernel32!GetModuleHandleW
+0x16e
0022cbfc 7c80b760 7ffdec00 0022cc14 77c39d23 kernel32!GetModuleHandleW
+0x1f
0022cc08 77c39d23 77c140a4 0022cc24 77c39e78 kernel32!GetModuleHandleA
+0x1f
0022cc14 77c39e78 00000001 006d23ef 0022cc38 msvcrt!strerror+0x2b29
0022cc24 77c39e90 00000001 00000000 006d23e8 msvcrt!initterm+0x111
0022cc38 004025d8 00000001 00000001 0022ffe0 msvcrt!exit+0x12
0022cc58 00406a1f 00000001 00000000 00000000 adb+0x25d8
0022ff58 00403068 00000001 006d2430 00413ce0 adb+0x6a1f
0022ff78 0040124b 00000003 006d2428 006d42a0 adb+0x3068
0022ffb0 00401298 00000001 00000009 0022fff0 adb+0x124b
0022ffc0 7c817077 00000001 00000002 7ffdf000 adb+0x1298
0022fff0 00000000 00401280 00000000 78746341 kernel32!
RegisterWaitForInputIdle+0x49



2) // this is the stack trace when trying to manually reproduce the
adb hang failure
0022ca30 7c901046 0197b178 7c9175e2 7c97b178 ntdll!KiFastSystemCallRet
0022cb24 7c80ac87 662b0000 0022cb58 00000000 ntdll!
RtlEnterCriticalSection+0x46
0022cb38 71a676a7 662b0000 00000000 0022cb74 kernel32!FreeLibrary+0x19
0022cb48 71a678d5 0022cb58 00c11ef0 00000000 mswsock!StartWsdpService
+0x1ae
0022cb74 71abd983 0022cba0 00c12620 0022cbbc mswsock!StartWsdpService
+0x3dc
0022cb84 71aba48e 0022cba0 00c11ed8 00c12620 ws2_32!
WSAUnhookBlockingHook+0x47b
0022cbbc 71ab2e96 00000000 00c11f10 7c8329aa ws2_32!WSAStringToAddressA
+0xd29
0022cbd8 71ab91b0 71ab9002 00000000 00000000 ws2_32!htons+0x43
0022cbfc 71ab9118 00000001 0041d6cb 00000001 ws2_32!WSCGetProviderPath
+0x389
0022cc18 77c39e24 006d4f92 0022cc38 77c39e90 ws2_32!WSCGetProviderPath
+0x2f1
0022cc24 77c39e90 00000001 00000000 006d4f8b msvcrt!initterm+0xbd
0022cc38 004025d8 00000001 00000001 0022ffe0 msvcrt!exit+0x12
0022cc58 00406a1f 00000001 00000000 00000000 adb+0x25d8
0022ff58 00403068 00000001 006d4fd8 00413ce0 adb+0x6a1f
0022ff78 0040124b 00000003 006d4fd0 006d3758 adb+0x3068
0022ffb0 00401298 00000001 00000009 0022fff0 adb+0x124b
0022ffc0 7c817067 7c91639b c0150008 7ffdd000 adb+0x1298
0022fff0 00000000 00401280 00000000 78746341 kernel32!
RegisterWaitForInputIdle+0x49

I was wondering if anybody has seen this issue before and if there is
any workaround or solution for this.

Thanks,
BDB