Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
as I think I can answer this question to myself by reading the MSDN description of closesocket, I want to have it confirmed by one of the experienced guys since the MSDN kinda only implies it from what I’ve read.
Is WSAENOBUFS a symptom of missing closesocket calls to used sockets ?
The occurence of
WSAENOBUFSerror messages does not necessarily mean that it is a symptom of missing closesocket calls. But it might be.The system responds with this message if you have not the necessary resources and or there are too many open sockets. However it might also be that you close everything appropriately but you try to open too much sockets or have no resources left.