> > For some reason, you call PutDataInSendBuffer after it has already been > > freed. > > After the object was freed, or the buffer was freed? Keep in mind that > I just called WSocketThrdServer.Free, so it was problably destroying > the object while it was attempting to send...?
I think freeing the server object will free all connection objects which each will free the buflist. > If so, how can I prevent this? Make sure all connections are closed/aborted before freeing the server object. And as usual, at the application level don't store a reference to a connection object because that reference may become invalid when the object is freed. If you need to store a reference somewhere, then you must code a notification mechanism, probably from the destructor of your client class. -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
