🚀 go-pugleaf

I have been exeriencing a number of memory leaks/codeguard errors in a
Builder Database App. I have managed to get a very short example to
fail every time ... Real rocket science stuff ;0)

4 buttons on a form, a socket connection to 127.0.0.1, a client
dataset to *ANY* exported dataset, a midas server app

//---------------------------------------------------------------------------
void __fastcall TForm1::Button1Click(TObject *Sender)
{
    SocketConnection1->Open();
}
void __fastcall TForm1::Button2Click(TObject *Sender)
{
    ClientDataSet1->Open() ;
}
void __fastcall TForm1::Button3Click(TObject *Sender)
{
    ClientDataSet1->Close() ;
}
void __fastcall TForm1::Button4Click(TObject *Sender)
{
    SocketConnection1->Close() ;
}
see I said it was rocket-science level !

ok, without the midas app server running ...
1)start my test application and close program - all ok
2)start my test application, click button1 to connect to the midas
server - which starts up, CPU window opens debuggng ntdll.dll ?!? and
close program - all ok
3)start my test application, click button1 to connect to the midas
server - click button 4 to close midas server and close program - all
ok
4)start my test application, click button1 to connect to the midas
server, then button2 to make CDS active (have tried both Open() and
Active=true - now no matter what i do, at the final close of the
program, I have lost 200 bytes with "The memory block (address) was
never freed, 0xEEEEEEEEEE, 200 bytes was aloocated with SysGetMem

I *cannot* believe that I am the only one experiencing this behaviour
- anyone found a fix/workaround/mystical communication from TeamB or
Borland about it ?

TIA
Rob
--
mailto:rob at critbank dot com