I'm using tLTcp with tLEventer. I've set tLTcp.eventer to the associated tLEvent object and call tLEvent.callAction to wait for new events. After a socket disconnected, OnDisconnect gets called shipped with an aSocket:tLSocket parameter. Should I call aSocket.destroy explicitly to prevent the disconnected aSocket from leaking the memory?
Mailing lists / fpc-pascal / 2012-04
does disconnected tLSocket auto destroy in lnet
2 messages · 1 person · –
- ZHANG Dao-yuan 2
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
ZHANG Dao-yuan wroteI'm using tLTcp with tLEventer. I've set tLTcp.eventer to the associated tLEvent object and call tLEvent.callAction to wait for new events. After a socket disconnected, OnDisconnect gets called shipped with an aSocket:tLSocket parameter. Should I call aSocket.destroy explicitly to prevent the disconnected aSocket from leaking the memory?
Ok, the problem is resolved. We don't worry about it since thess memory is handled by Lnet.