Article View: borland.public.cppbuilder.database.ado
Article #174Re: TADOQuery Memory Leak
From: Clayton Arends
Date: Thu, 03 May 2007 15:12
Date: Thu, 03 May 2007 15:12
18 lines
2087 bytes
2087 bytes
> I have reproduced the problem in a simple console app. Loop in main(), > create the TADOConnection, open, close and delete it. Sleep for 20 > seconds, rinse and repeat. It looks like you've done that part of the test for me. Your application situation is very similar to mine. I have a service app that is part of a 3-tier database solution. Memory leaks have been a problem for us since we use ADO exclusively at that level. The problem is so pervasive that we are building into the app a scheduled nightly "restart" of our service so that the OS can clean up all of the memory leaks. The next test I can try (or someone else can) would be to import the ADO COM directly and use those interfaces rather than the ones supplied by Borland. This test will rule in/out the VCL as being the root of the cause. I'll try to get to that this weekend. - Clayton
Technical Details
Message-ID:
<4639fba7$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!newsgate.cistron.nl!xs4all!news2.euro.net!newsfeed.freenet.de!newsfeed00.sul.t-online.de!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> <4636da37@newsgroups.borland.com> <463779b7$1@newsgroups.borland.com> <4639e7d7$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: "Clayton Arends" <nospam_claytonarends@hotmail.com> 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> <4636da37@newsgroups.borland.com> <463779b7$1@newsgroups.borland.com> <4639e7d7$1@newsgroups.borland.com> Subject: Re: TADOQuery Memory Leak Date: Thu, 3 May 2007 08:12:01 -0700 Lines: 20 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: 71.93.4.10 Message-ID: <4639fba7$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1178205095 71.93.4.10 (3 May 2007 08:11:35 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!newsgate.cistron.nl!xs4all!news2.euro.net!newsfeed.freenet.de!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail