Re: BSTR memory leak
Finally, make sure you have no methods with pure [out]
arguments (e.g. neither [in, out] nor [out, retval]). These
about guarantee you memory leaks in Automation as they
are silently promoted to [in, out] - something clearly not
anticipated by your code so nobody frees the client-side
older value.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Herby" <prmarjoram@gmail.com> wrote in message
news:1169669141.907880.190550@m58g2000cwm.googlegroups.com...
On 24 Jan, 16:56, "Brian Muth" <b...@mvps.org> wrote:
What can anyone say? You have a memory leak which you haven't tracked
down.
You have some debugging to do.
Brian
Well im not so sure. It seems more like a system level problem.
Part of solving the problem is trying to get some feedback off here.
There are some similar threads to do with leaks being experienced
through BSTR.
The COM component allocates a BSTR.
When the client script ends - I would expect any allocated memory to be
freed
Only the script held references to these BSTR objects.
This is simply not happening. The BSTR memory is not being freed!
Unfortunately i cannot look under the hood or at the source.