Would calling RIOReceive() on a closed socket potentially cause a crash?

Question

Hello, I would like to inquire about a crash that occurred when calling the RIOReceive() function.

Please understand that the sentences may be strange because I used a translator.

What happens is that thread A performs closesocket(sock) on the previously connected socket sock,

When thread B attempts RIOReceive(rq, ...) for RIO_RQ rq connected to the corresponding socket,

Occasionally, mswsock.dll crashes during execution of the RIOReceive() function.

Additionally, in MSDN's LPFN_RIOCREATEREQUESTQUEUE callback function document,

'As request queues are closed by closing the sockets using the closesocket function, those slots will be freed up for use by other sockets.'

There is a sentence, and I would like to also inquire about what slots refers to here.

Thank you for your attention to this matter.

Answer 1

Whether you call closesocket() first and then call RIOReceive（)?

When you call the closesocket function, the request queues (RIO_RQ structs) are closed.

An application must obtain a RIO_RQ for a Winsock socket, and then the application can use the RIOSend, RIOSendEx, RIOReceive, or RIOReceiveEx functions.