TcpClient.BeginAcceptTcpClient / Socket.BeginAccept / all other variations...

I've been having a problem with the use of any of the async methods of TcpClient, Socket, etc eating >95% cpu after receiving the first connection. I've been working on this for over a week now and I'm unable to find references to this issue anywhere. I've tried every way I can think of to work around this problem.

Even if no data is sent or received on the connection....or if I close the received connection -- some unknown thread uses all the available cpu power after the first connection occurs.

I created a small project that reproduces the problem -- I've zipped it up and posted it here:

http://www.profitfuel.net/TcpClientProblem.zip

If anyone knows how to fix this, please let me know.

Thanks,
- Joshua Garvin

[886 byte] By [JoshuaGarvin] at [2007-12-24]