zayin wrote: >> but unless is cumulative it really does not matter. > > I concur. It is just a pain. > > IMHO, there should be some step(s) to close the clients and close the > server and not have a memory leak.
I've never seen that leak, anyway Close server's listening socket in order to disable new connections before destroying/closing all connected clients and freeing the TWSocketServer object. As I wrote before the allocated memory is either freed when the message is handled (the default) or when the call to PostMessage() failed, so the only case where a leak may happen is when PostMessage() succeeded however that message is never handled (happens, for instance, _if the destination Window has been destroyed after the call to PostMessage). -- Arno -- 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