Markus Humm wrote:
>> Markus Humm wrote:
>>
>>> My problem now is that FastMM reports a memory leak when the
>>> application is terminated.
>>
>> The report attached says that an attempt has been detected to call
>> a virtual method on a freed object. That isn't a memory leak.
>
> Yes I know. Wh
> Markus Humm wrote:
>
>> My problem now is that FastMM reports a memory leak when the
>> application is terminated.
>
> The report attached says that an attempt has been detected to call
> a virtual method on a freed object. That isn't a memory leak.
Yes I know. When I use the fulldebug switch
Arno Garrels wrote:
[..]
> May be the next connection is accepted too early? You could post
> a custom message from OnSessionClosed and free and nil the
> ClientWSocket
> from the message handler in order to be sure.
[..]
Please forget this part of my last message.
--
Arno Garrels [TeamICS]
http
Markus Humm wrote:
> My problem now is that FastMM reports a memory leak when the
> application is terminated.
The report attached says that an attempt has been detected to call
a virtual method on a freed object. That isn't a memory leak.
> The rest of the app. works well enough, I
> can conne
Hello,
my communication layer uses a TWSocket as TCP server socket and one for
the actual communication as there will only be one connection at any
give time. When the client requests a close of the connection I close
the socket and in the OnSessionClosed I free it, because the server
socket d
