Article View: borland.public.cppbuilder.database.ado
Article #1290Re: TADOQuery and a memory leak?
From: Graham Thompson
Date: Tue, 03 Aug 2004 11:04
Date: Tue, 03 Aug 2004 11:04
17 lines
1387 bytes
1387 bytes
> The problem is, the app appears to be leaking memory like a sieve.
>
> Has anyone seen anything like this before?
OK, I've found a little more out about the problem ... the leak appears to
be at the point where the update criteria is changed, i.e.:
Recordset->Properties->Item[WideString("Update Criteria")]->Value = 0;
We set this when the query goes active, and have about 50Kb allocated that
hangs around even after the instance is deleted.
Any clues??
Thanks again,
GT.
Technical Details
Message-ID:
<410f712f$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!proxad.net!gatel-ffm!gatel-ffm!194.25.134.126.MISMATCH!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<410e4309$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10698b,fce6e3cdc92d4640 X-Google-Attributes: gid10698b,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Graham Thompson" <gct@faGUESS-WHAT-TO-DO-WITH-THISsl.co.uk> Newsgroups: borland.public.cppbuilder.database.ado References: <410e4309$1@newsgroups.borland.com> Subject: Re: TADOQuery and a memory leak? Date: Tue, 3 Aug 2004 12:04:15 +0100 Lines: 19 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 NNTP-Posting-Host: 62.173.124.106 Message-ID: <410f712f$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1091531055 62.173.124.106 (3 Aug 2004 04:04:15 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!proxad.net!gatel-ffm!gatel-ffm!194.25.134.126.MISMATCH!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail