Article View: borland.public.cppbuilder.database.ado
Article #172Re: TADOQuery Memory Leak
From: Patrick Wong
Date: Thu, 03 May 2007 03:58
Date: Thu, 03 May 2007 03:58
36 lines
2955 bytes
2955 bytes
"Clayton Arends" <nospam_claytonarends@hotmail.com> wrote in message news:4636005c$1@newsgroups.borland.com... >I found time off and on during the week to test this issue. I made two >test applications. One in BCB6 and one in BDS2006 Delphi personality. >Both applications were built standalone. Both applications yielded almost >identical results. Memory consumption was measured using a custom memory >usage function and the Windows Task Manager. I have included my BCB6 test >code at the end of this post if anyone wishes to double-check my test and >results. > > At one point, to rule out the VCL implementation of ADO, I rewrote the > test to use the raw ADO interface classes (_Connection, and _RecordSet) > with similar memory leak results. > Grateful for your effort. Since the root cause is still a mystery, I rewrote the database access routine with DBExpress for trial. I also let the application run over night and the test shows that using DBExpress the significant memory growth over time does not happen anymore. > > I performed some general searches for ADO memory leaks and found some > scattered references. Many threads concluded that the leaks were caused > by misuse of the ADO objects. Some concluded that certain versions of ADO > drivers were causing the leaks. A majority had no conclusions. It is > hard to know for sure what is going on here. > In this thread http://groups.google.ru/groups?hl=ru&lr=&threadm=41ed54ce%241%40newsgroups.borland.com&rnum=6&prev=/groups%3Fas_q%3DTADOCommand%26as_ugroup%3D*borland*%26as_scoring%3Dd%26lr%3D%26num%3D20%26hl%3Dru some people said they spot the problem, while other claimed that the fix was already applied to Delphi 7. But I find both my BCB6 and BDS2006 are still having the old code. If anyone can kindly have a trial please let me know the result. Thanks in advance.
Technical Details
Message-ID:
<46395dc9$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!proxad.net!212.101.4.254.MISMATCH!solnet.ch!solnet.ch!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<462d7a19$1@newsgroups.borland.com> <462f9b39$1@newsgroups.borland.com> <462ffa42$1@newsgroups.borland.com> <463018d2$1@newsgroups.borland.com> <4636005c$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10698b,f6b9f007fd37682e X-Google-Attributes: gid10698b,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Patrick Wong" <patrickwong@computer.org> Newsgroups: borland.public.cppbuilder.database.ado References: <462d7a19$1@newsgroups.borland.com> <462f9b39$1@newsgroups.borland.com> <462ffa42$1@newsgroups.borland.com> <463018d2$1@newsgroups.borland.com> <4636005c$1@newsgroups.borland.com> Subject: Re: TADOQuery Memory Leak Date: Thu, 3 May 2007 11:58:01 +0800 Lines: 38 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-RFC2646: Format=Flowed; Response NNTP-Posting-Host: 203.82.254.252 Message-ID: <46395dc9$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1178164681 203.82.254.252 (2 May 2007 20:58:01 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!proxad.net!212.101.4.254.MISMATCH!solnet.ch!solnet.ch!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail