support mailing
Onderwerp: Re: [twsocket] Loosing memory in TWSocketClient.TriggerSessionClosed
Henk van der Meer wrote:
> The thing is that if you leave the freeing up to windows you have no
> means of checking for memory leaks.
> So I like my programs to free all their memory so I'
gt;
>
> -Oorspronkelijk bericht-
> Van: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org]
> Namens Arno Garrels
> Verzonden: woensdag 21 september 2011 16:10
> Aan: ICS support mailing
> Onderwerp: Re: [twsocket] Loosing memory in
> TWSocketClient.TriggerSessio
support mailing
Onderwerp: Re: [twsocket] Loosing memory in TWSocketClient.TriggerSessionClosed
Henk van der Meer wrote:
> Hello,
>
> I have an application that uses fastmm4 to track memory.
> It informed me of an memory leak that I traced down to:
> TWSocketClient.TriggerSessionClo
Henk van der Meer wrote:
> Hello,
>
> I have an application that uses fastmm4 to track memory.
> It informed me of an memory leak that I traced down to:
> TWSocketClient.TriggerSessionClosed
>
> This procedure does a New(PIdRec);
> This record is only disposed of when the postmessage returns tr
Hello,
I have an application that uses fastmm4 to track memory.
It informed me of an memory leak that I traced down to:
TWSocketClient.TriggerSessionClosed
This procedure does a New(PIdRec);
This record is only disposed of when the postmessage returns true.
In my program this isn't the case.
D
