Hi, the only thing that i've seen similar to what you report had to do with Panda antivirus. When the connection was closed during a begin something, the callback was not invoked.
Manuel ----- Original Message ----- From: "Garry Barclay" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 21, 2004 1:09 PM Subject: [ADVANCED-DOTNET] Missing callbacks from asynchronous sockets? > It appears that we are NOT receiving the (completion port) callback from > an asynchronous socket (BeginSend/EndSend) call. > > The sockets are clients and the failure seems to be related to shutdowns > on the socket. > > This has the effect of leaving a pinned GCHandle on the heap (pinning the > send buffer). We've checked the process memory dump with WinDbg and have > seen that the sockets are shutdown successfully. Checking the Socket class > implementation (v1.1) with Reflector it's seems clear that IF the callback > is made then the buffer should always be unpinned. > > We've added in static counters using interlocked.xxx to verify that the > calls are definitely not reaching our code, and this confirms our > suspicions. > > Because of the pinned buffers, heap compaction can't take place and we end > up with high memory usage figures even though most of the heap is free > space between those buffers. > > Anyone seen something like this before? > > =================================== > This list is hosted by DevelopMentorŪ http://www.develop.com > Some .NET courses you may be interested in: > > NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles > http://www.develop.com/courses/gaspdotnetls > > View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
