COM C# Memory leak Tracing
Posted
by maxfridbe
on Stack Overflow
See other posts from Stack Overflow
or by maxfridbe
Published on 2009-02-05T21:15:15Z
Indexed on
2010/04/14
9:53 UTC
Read the original article
Hit count: 510
Is there a way to find out the memory usage of each dll within a c# application using com dll's? Or what would you say is the best way to find out why memory grows exponentially when using a com object (IE. Whether the COM object has a memory leak, or whether some special freeing up of objects passed to managed code has to occur(and/or how to do that)).
© Stack Overflow or respective owner