🚀 go-pugleaf

Well, I think for one I am getting bit by the TThread memory leak,
which I will probably fix by writting my own version. 

For the most part, if you run any of the memory checkers I mentioned
below, you will find that there are a lot of leaks attributed to the
Builder DLLs. Of course, without having bothered to build the
libraries with debugging enabled, I am not able to be more specific
regarding where these DLLs are leaking.

Otherwise, if I turn off checking for all DLLs and apps other than my
own, I find that the memory consumption is stable and leak free.

On Wed, 13 Oct 1999 19:45:53 -0400, "Chris Uzdavinis (TeamB)"
<chris@uzdavinis.com> wrote:

>Do you use exceptions very often?  There are several exception bugs in BCB3
>that can result with VCL exception objects not being deleted when caught in
>C++ code.  I don't know of any other leaks.  (Though there easily could be
>some.)
>
>Anyway, I do know that BCB4 does fix the exception bugs of BCB3.  As for
>your leaks (which sound like something else) I have no idea if they're fixed
>or not.  But I'm still not sure what the actual problem is you're
>experiencing.
>
>Chris (TeamB)
>
>
>
>Bill wrote in message <3804caea.4493887@forums.inprise.com>...
>>I am plagued with VCL and cp3240mt.dll memory leaks using C++ Builder
>>v3.0.  My application runs in the tooltray and so is always present,
>>consuming copious amounts of memory over time. Looking at the task
>>manager under NT shows that my app is the biggest kid (or pig) on the
>>block!
>
>
>