Die-hard COM Processes

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Phil Galey - 17 Nov 2005 19:33 GMT

I have a VB.NET application that instantiates a COM object from a DLL using
New(). As the application is closing, it sets the object to Nothing and
does a GC.Collect, but the process does not get removed from memory. It
remains running and listed in Task Manager.

Even if I create a process object using GetProcessesByName and then close or
kill the process, it still persists and GetProcessesByName still finds that
process running.

Does .NET have a "bigger hammer" for bidding fairwell to stubborn processes
like this one? Thanks.

Reply to this Message

Phil Galey - 21 Nov 2005 16:34 GMT

Problem solved by powering down completely.

> I have a VB.NET application that instantiates a COM object from a DLL using
> New(). As the application is closing, it sets the object to Nothing and
[quoted text clipped - 7 lines]
> Does .NET have a "bigger hammer" for bidding fairwell to stubborn processes
> like this one? Thanks.

Reply to this Message

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...