Winsock error
While our program runs (with some FTP handling and some pings trought ICMP sockets) we get sometimes a (partial) system stop
I got this error in my log file, seems to be a lack of resources.
WSAENOBUFS
(10055) No buffer space available.
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
I see my application blows up with performance monitor and the number of threads are increasing. Probably because I open a new socket before the old one was closed completely.
Is there a way to check if a created socket has been closed down?
What are the most common booby traps in this style of programming?
Thanks,
Dries
|