🚀 go-pugleaf

> VB does have a primitive (reference count) garbage collector.

Depending upon how the code was written the garbage collector may not be
involved.  The collector may handle normal VB allocations, but not
necessarily ones requiring that SysFreeString be called and in fact if it
does not handle it, what you suggest is happening is the exact result one
could expect.  The code you showed has no memory leak.  Look at the VB code.

.  Ed

> Fernando wrote in message
> news:2j7g0012sja7vhngl777130qbb0sp4163k@4ax.com...
>
> >I do not know that Visual Basic handles it automatically.
>
> VB does have a primitive (reference count) garbage collector.
>
> >  It all depends
> >upon the code the writer of the VB part used.
>
> That's me. :-) I just call the function and save the result in a VB string
> (BSTR).
> >You said that CodeGuard did not find any leaks yet there is a memory
leak.
> >How do you determine that there is a memory leak?
>
> Well... actually CodeGuard doesn complain if I call that function from
with a
> test exe (within the BCB ide). However, if I create a dll (with code guard
> enabled) and call it from VB, then I do get a messagebox from CodeGuard
> complaining about a memory leak. :-?
>
> If I run the VB code that call that function in the dll in a loop, memory
> usage goes up pretty quickly.