Article View: borland.public.cppbuilder.database.ado
Article #162Re: TADOQuery Memory Leak
From: Clayton Arends
Date: Wed, 25 Apr 2007 18:20
Date: Wed, 25 Apr 2007 18:20
5 lines
1129 bytes
1129 bytes
I forgot to ask. Another point of memory leak could be the destruction of your threads. You didn't show how you are deleting them. Are you setting FreeOnTerminate to true or are you deleting the thread in some other way? - Clayton
Technical Details
Message-ID:
<462f9bbe$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<462d7a19$1@newsgroups.borland.com> <462f9b39$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> Subject: Re: TADOQuery Memory Leak Date: Wed, 25 Apr 2007 11:20:04 -0700 Lines: 7 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: <462f9bbe$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1177525182 71.93.4.10 (25 Apr 2007 11:19:42 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail