I found the ICS bug: when I put the below in the ThttpCli descendent's
destructor, it works:
SetWindowLong(FWindowHandle, 0, 0);
SetWindowLong(FCtrlSocket->Handle, 0, 0);
In THttpCli destructor, the destruction order of the CTrlSocket is first so
I think that's why it leaks the window. And no, CodeGuard/Memproof/Eurekalog
cannot show undeleted windows.
----- Original Message -----
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing" <email@example.com>
Sent: Saturday, February 04, 2006 1:28 PM
Subject: Re: [twsocket] Remember the SetWindowLong bug in WSocket?
> Fastream Technologies wrote:
>> That bug caused a lot of frustration here. Now the problem is resolved
>> FTP and web servers with my fix BUT for the reverse proxy, there is a
>> window leakage that cannot be detected by CodeGuard. It seems the problem
>> is in THttpCli destructor. XWindowDealloc returns true but I have BIG
>> doubts. It is a bit confusing because in THttpCli there are two handles
>> and two windows! One is for the THttpCli and the other one is for
>> THttpCli->CtrlSocket. Could someone take a look? It leaks 40KB per
> Have you cross-checked one of the THttpCli demo projects?
> Here MemProof says "No leak found" (beside 1x 4k in MakeObjectInstance
> is normal..).
> Arno Garrels [TeamICS]
>> Best Regards,
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://www.elists.org/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be