• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 365
  • Last Modified:

Clean unmanaged memory from .net

Hi Experts - Lets say I have .net code that makes a bunch of COM calls, and sometimes I fail to call Marshal.FinalReleaseComObject().  Over time I get a memory leak.  Is there a way to search (unmanaged?)  memory and release these COM objects?  Or do I have to release the object just as soon as I'm done with it?  I'm trying to cleanup after the fact. =)

0
sfun28
Asked:
sfun28
  • 3
1 Solution
 
sfun28Author Commented:
Hi rpkhare - these resources don't quite help.  Let me restate my question: I'm looking for a way to enumerate through all of the Runtime Callable Wrappers that my app has created.

for example my code may get the following RCW, but never release the object
dim abc as SomeCOMObject = ComObj.GetAnotherComObject

I'd like a way, in some other thread or object, to enumerate the various live RCWs and free them.  is that possible?
0
 
sfun28Author Commented:
rpkhare or others?
0
 
sfun28Author Commented:
no answer so closing out
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now