COM Object Cleanup

Question

I am instantiating a COM object from a VBA script in excel as defined in a C# dll. The C# class I instantiate has a finalizer that performs garbage collection, notably other MS Office objects it references, which I should see appear and disappear in the task manager. In fact, the unit tests demonstrate that an Office process appears when the dll is called, and goes away when it is finished.

When the dll is called from the VBA, I have noticed that the processes remain open after the VBA function ends, i.e. the object is notcleaned up after being called, which leads me to believe that VBA does not release the COM object.

My function looks something like this:

Function Raz(inp As String)
 Dim o: Set o = CreateObject("foo.bar")
 o.InputFields.FirstInput = inp
 o.Update
 Raz = o.OutputFields.FirstOutput
End Function

I have added the following line at the end of the function in order to resolve the issue:

set o = Nothing

However, the resources in my COM process remain after execution and completion of my VBA script. How do I garbage collect my COM objects from VBA without manually creating a dispose call?

Joel Spolsky · Accepted Answer · 2010-12-13 22:24:29Z

4

COM will keep processes in memory for a while after the last reference is gone, just in case you want to create another object requiring the same process soon afterwards.

The theory is that process creation is very slow and expensive, and you might inadvertently write a loop or something that does this:

 While 1=1

      Set a = CreateObject(...)
      ' Later
      Set a = Nothing

 Wend

You wouldn't want Windows thrashing around killing and launching processes endlessly in the loop.

Eventually they go away.

answered Dec 13, 2010 at 22:24

Joel Spolsky

33.8k18 gold badges91 silver badges105 bronze badges

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

Comments

rfb · Accepted Answer · 2014-02-08 08:35:21Z

2

You have a weak reference to the created object, Raz function return value, that maintains the object instance.

Variable o is automatic and referenced object is automatically set to nothing when function returns, but you are assigning value to Raz and probably to client code so the instanced value is not disposed on function return.

Furthermore, if the object, as it happens, reference a user control, you probably can't unload the user form containing it.

edited Feb 8, 2014 at 8:35

answered Jan 31, 2012 at 15:41

rfb

1,1871 gold badge7 silver badges14 bronze badges

Comments

Lance Roberts · Accepted Answer · 2011-09-07 14:17:22Z

1

In VBA the command to release an object is

Set o = Nothing

edited Sep 7, 2011 at 14:17

answered Nov 15, 2010 at 17:33

Lance Roberts

22.9k32 gold badges115 silver badges132 bronze badges

4 Comments

tbischel Over a year ago

so I tried that, and the finalizer still doesn't get called. I ended up implementing IDisposable and manually disposing resources, in combination with the set o = Nothing line... I don't know if everything gets released but at least the dispose releases the big things.

Caltor Over a year ago

Could you give some more explanation of how you implemented IDisposable please? I have the same problem with a Visual Foxpro 9 COM server I have written. Thanks.

Lance Roberts Over a year ago

@Caltor, you need to @tbischel to get his attention (only the first @ works, so you still need to do it yourself).

Caltor Over a year ago

@Lance-Roberts Thanks for the @ tip. I think it's a moot point now anyway as per stackoverflow.com/questions/7333134/…

Collectives™ on Stack Overflow

COM Object Cleanup

3 Answers 3

Comments

Comments

4 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

4 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related