Subject | Re: Checking connection in advance to connecting |
---|---|
Author | Adam |
Post date | 2005-07-04T23:17:38Z |
Nando / George,
When I was using C a number of years back I did encounter a similar
issue where part of the struct did in fact not release memory
(WSACleanup wasn't doing its job properly), and the only way I got
around it back then was to do it in a different thread.
Since working in delphi, I have never experienced that sort of issue.
I am happy to accept that I might have missed freeing something back
in my C days. By the way if opening a socket is what is causing this
leak, then you are going to get just as many memory leaks using pings
or TIdTCPClients etc, because these too need to use a socket.
Does the leak occur when the server is contactable or only when it is
unreachable? Are you dynamically creating it or is it added at design
time? It is probably a question for the IBO list though because it
seems like either:
a) A leak caused by IBOs connect or
b) IBOs connect not being used correctly
Adam
When I was using C a number of years back I did encounter a similar
issue where part of the struct did in fact not release memory
(WSACleanup wasn't doing its job properly), and the only way I got
around it back then was to do it in a different thread.
Since working in delphi, I have never experienced that sort of issue.
I am happy to accept that I might have missed freeing something back
in my C days. By the way if opening a socket is what is causing this
leak, then you are going to get just as many memory leaks using pings
or TIdTCPClients etc, because these too need to use a socket.
Does the leak occur when the server is contactable or only when it is
unreachable? Are you dynamically creating it or is it added at design
time? It is probably a question for the IBO list though because it
seems like either:
a) A leak caused by IBOs connect or
b) IBOs connect not being used correctly
Adam