🚀 go-pugleaf

> The TADOConnection and TADOQuery objects are declared as private members
> of  the thread and created at the thread's constructor.  Is it still an
> issue calling CoInitalize() and CoUninitialize() in the thread's context?

I'm not exactly sure what you mean by "is it still an issue".  Any code
that is executed in a thread's constructor and destructor are executing in
the context of the main application thread.  TThread descendants don't start
executing in their own context until Execute() is invoked.

However, I took another look at my test app that replicates your behavior.
I thought the by additionally calling OleInitialize() in the main
application thread the memory leak went away.  But, it appears that I was
mistaken.  I am currently trying to figure out what is going on here.

>>> Application->ProcessMessages();
>>
>> Don't call this from within any thread other than the main application 
>> thread.
>
> Comment out that does not help.

I didn't say it would help ... just don't do it. ;-)

- Clayton