.NET COM interoperation - Fighting with RCW memory leaks

bChen@sh

Rate me:

4.60/5 (7 votes)

9 Aug 2012CPOL7 min read

26.9K

This article explores the rules of how AddRef and Release are called in RCW and COM, which addresses the issue of RCW memory leaks.

Revisions

Compare	Revision	Minor	Date	Status	Editor
	8 - publicly available	Yes	9-Aug-12 19:43	Available	bChen@sh
The article has been approved
	7	No	9-Aug-12 17:01	Pending	bChen@sh
RCW reference to underlying COM can be more than one!
	6	No	16-Mar-12 4:26	Available	Sean Ewington

	5	No	15-Mar-12 20:25	Composing	bChen@sh

	4	No	15-Mar-12 17:47	Composing	bChen@sh

	3	No	15-Mar-12 17:39	Composing	bChen@sh

	2	No	15-Mar-12 5:41	Available	Smitha Nishant

	1	No	14-Mar-12 21:24	Composing	bChen@sh

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Written By

bChen@sh

Software Developer

China

I've been a developper for almost 5 years. I've my developping background mostly on .net and c++. I've also got chance to written tens of thousands of lines sql procedures/ and funcctions Wink | ;-)

.NET COM interoperation - Fighting with RCW memory leaks

Revisions

License

Comments and Discussions