How to deallocate COM server object forcefully from C# .NET

Question

Can I know how to deallocate COM server object forcefully from C# .NET if particular condion fails or the object is partially constructed?

The problem is I am using that COM server using DCOM mechanism; in the worst case, when the object is not created fully and I am coming out of application since failure, the COM object is still in memory (showed in COM+ Application component services). If its going beyond some limits, it leads to memory leak and crash. But if its manageable amount of failures, its getting deleted after some point of times.

Sample:- Calculator.App objApp = new Calculator.App();

if( !obj.CanBeUsed() ) { //how to deallocate the COM object objApp }

Note: There is a method GC.Collect() used by Garbase Collector to de-allocate from the heap memory forcefully. Whether I can use this method or .NET franework is giving anyother solution for this particular case?

Thanks for ur comment on that, Aamir. I will work on that in future. I was not aware of that, thanks again. — Snabak Vinod
– Snabak Vinod, Commented Oct 21, 2010 at 11:49

Aamir · Accepted Answer · 2010-10-21 11:37:46Z

2

Like this:

System.Runtime.InteropServices.Marshal.ReleaseComObject(objApp);

answered Oct 21, 2010 at 11:37

Aamir

15.8k6 gold badges49 silver badges72 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Snabak Vinod Over a year ago

There is a MSDN blog saying using ReleaseComObject() is very dangerous. blogs.msdn.com/b/visualstudio/archive/2010/03/01/…. You have any points on that?

Aamir Over a year ago

You talked about releasing the object forcefully, right? Whenever you will do something forcefully, there will be side-effects :)

Snabak Vinod Over a year ago

Here side effect shouldn't happen :(. I am going to use for avoiding memory leak only, to help .NET framework :).

Jakub Šturc · Accepted Answer · 2010-10-21 11:38:37Z

1

You should try Marshal.FinalReleaseComObject method.

The FinalReleaseComObject method releases the managed reference to a COM object. Calling this method is equivalent to calling the ReleaseComObject method in a loop until it returns 0 (zero).

When the reference count on the COM object becomes 0, the COM object is usually freed, although this depends on the COM object's implementation and is beyond the control of the runtime. However, the RCW can still exist, waiting to be garbage-collected.

The COM object cannot be used after it has been separated from its underlying RCW. If you try to call a method on the RCW after its reference count becomes 0, a InvalidComObjectException will be thrown.

answered Oct 21, 2010 at 11:38

Jakub Šturc

35.9k25 gold badges92 silver badges115 bronze badges

2 Comments

Aamir Over a year ago

This is a bit dangerous. From MSDN: "Releases all references to a Runtime Callable Wrapper (RCW) by setting its reference count to 0." This means that it will try to forcefully set the reference count to 0 which can be bad because there might be other valid references as well.

Snabak Vinod Over a year ago

There is a MSDN blog saying using ReleaseComObject() is very dangerous. blogs.msdn.com/b/visualstudio/archive/2010/03/01/….

Collectives™ on Stack Overflow

How to deallocate COM server object forcefully from C# .NET

2 Answers 2

3 Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related