Does it help track-down COM object "leaks"?

Want to evaluate dotMemory ASAP, but just curious if anyone has tried using it for tracking down COM object reference leaks in C# (VS2010, .Net 4)?

I think I'm having trouble getting a MS Office app to close due to an object not getting released properly.  Not sure, but really want to know if dotMemory will help me determine if that's the cause or not.

I try to use Marshall.ReleaseComObject() to release all the references I get, but maybe I'm missing one or something.

Appreciate any feedback about whether dotMemory might help!


1 comment
Comment actions Permalink


You can use dotMemory to track your COM objects. Do you know type name of your objects which should be resolved?  If you do, get snapshot after Marshall.ReleaseComObject() and use "Filter" in type list or "Group by namespace" or "Group by assembly" to ensure that your objects are gone. If there are none of these objects in the snapshot they are gone. If  they are presented open a set of them and use "Group by Dominators" or  "Group by similar retention" to find out why they are still in memory.


Sorry, my fail. Currently, dotMemory can't track COM objects.


Please sign in to leave a comment.