Method System.Runtime.InteopServices.Marshal.ReleaseCOMObject doesn't kill all object

Question

Why a dll registered into COM+ components has "Activated Count" equal 1 even if the caller process(.net 2.0 Assembly) always use the method System.Runtime.InteopServices.Marshal.ReleaseCOMObject() ?

ReleaseCOMObject really disactivate object if the counter is greater of 1 but remain always one object active until timeout expired.

pretty sure com ref counts have to be 0 before you release them? — asawyer, Mar 09 '11 at 16:16

score 0 · Accepted Answer · edited May 23 '17 at 12:19

0

This is very similar to another question on SO

Why use FinalReleaseComObject instead of ReleaseComObject?

Generally the remaining refcount indicates that there is another managed object holding onto a reference that has not yet been garbage-collected. (Usually the RCW)

edited May 23 '17 at 12:19

Community

1
1

answered Mar 09 '11 at 16:18

stephbu

5,072
26
42

Method System.Runtime.InteopServices.Marshal.ReleaseCOMObject doesn't kill all object

1 Answers1