Re: strange memory leak problem
- From: mdk <leun98@xxxxxxxxx>
- Date: Fri, 07 Sep 2007 00:28:01 -0000
I am a little bit confused. The DLL here I am talking about is the COM
component. And the final memory deallocation is done in the COM object
destructor. The problem is if calling _CrtDumpMemoryLeaks at this time
is meaningless when I should call it then? Thanks.
Timmy
On Sep 5, 10:12 pm, Joseph M. Newcomer <newco...@xxxxxxxxxxxx> wrote:
You can assume that calling _CrtDumpMemoryLeaks is meaningless at this point. It can only
report memory that has been allocated in the default heap and not deallocated, but this
has nothing to do with the DLL or its existence. So it is entirely possible that you will
have allocated memory at the time this DLL exits, that has been allocated by components
other than the DLL.
joe
.
- Follow-Ups:
- Re: strange memory leak problem
- From: Joseph M . Newcomer
- Re: strange memory leak problem
- References:
- Re: strange memory leak problem
- From: mdk
- Re: strange memory leak problem
- From: Joseph M . Newcomer
- Re: strange memory leak problem
- Prev by Date: Re: Code Page problem in SetWindowText
- Next by Date: Re: WinDiff done right?
- Previous by thread: Re: strange memory leak problem
- Next by thread: Re: strange memory leak problem
- Index(es):
Relevant Pages
|