Re: Managed VC++ crashing in debug build caused memory leaks
- From: "Ben Voigt" <rbv@xxxxxxxxxxxxx>
- Date: Tue, 14 Nov 2006 14:43:37 -0600
"PL" <paul@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:TKadnc1jZPjym8fYnZ2dnUVZ8tSdnZ2d@xxxxxxxxx
By the way, this is using .NET framework 1.1 - we can't upgrade to 2 yet!
PL wrote:
Hi everyone,
I was surprised to see memory leaks in our application when it crashed
today. Basically, the code is written in C#, but with c# and C++ DLLS;
its the latter (managed extensions) that cause the memory leaks (the new
operator in crtdbg.h). Does the garbage collector not work in debug build
for VC++?
Remember that only __gc objects are garbage collected, and the new operator
can also allocate from the native heap. This is distinguished a lot better
in C++/CLI, but you said you're stuck with .NET 1.1 :(
TIA
Paul
--
----
Home: http://www.paullee.com
Woes: http://www.dr_paul_lee.btinternet.co.uk/auto.shtml
.
- Follow-Ups:
- References:
- Prev by Date: Re: How to purposefully put an Assertion failure into Finalize() for debug builds using C++/CLI syntax?
- Next by Date: Re: How to purposefully put an Assertion failure into Finalize() for debug builds using C++/CLI syntax?
- Previous by thread: Re: Managed VC++ crashing in debug build caused memory leaks
- Next by thread: Re: Managed VC++ crashing in debug build caused memory leaks
- Index(es):
Relevant Pages
|
