PRB: WSACancelAsyncRequest Causes a Memory Access Violation |
Q140166
The information in this article applies to:
- Microsoft Win32 Software Development Kit (SDK), versions 3.51, 4.0
SYMPTOMS
An application that uses the WinSock 1.1 call WSACancelAsyncRequest occasionally throws memory exceptions or causes erratic behavior.
CAUSE
WSACancelAsyncRequest has unavoidable timing conflicts that make canceling calls in progress impossible. WSACancelAsyncRequest is only successful at stopping calls queued for processing that have not yet started.
RESOLUTION
Don't use WSACancelAsyncRequest to cancel calls that may be in progress. Specifically, don't try to cancel asynchronous selects. Allow them to complete, and ignore the results if necessary.
STATUS
This behavior is by design.
MORE INFORMATION
When an asynchronous WinSock call is in progress, it is hard to stop. For example, an outstanding WSAAsyncSelect call may be in the process of writing to a buffer your application supplied. The sockets DLL has no way of terminating a memory copy because of the timing windows generated by multiple threads. One thread may be in the middle of copying while another does the cancel.
The best way to cancel asynchronous events is to allow them to complete, but ignore the results. For WSAAsyncSelect, you might set a status flag, and when the select message is processed by your window procedure, you can check the status flag, ignoring the message if the flag is set.
Keywords : kbnetwork kbtshoot kbAPI kbOSWinNT351 kbSDKPlatform kbOSWin95 kbGrpDSNet
Issue type : kbprb
Technology : kbWin32SDKSearch kbAudDeveloper kbSDKSearch kbWin32sSearch kbWin32SDK400 kbWin32SDK351
Last Reviewed: March 8, 1999 |
