This is probably old news, but I believe that the COM interop is leaking.  I
have a C++ COM server class (in process) that creates a thread, initialises
COM for the thread, and then repeatedly calls an event method that has no
parameters or return value.  On the .NET side, in C#, the event handler does
something trivial with it, or does nothing at all.  

The result is a constantly increasing process page file size, even though
the CLR profiler claims to have stable heap usage.  I have a customer getting
caught with this, so it's a bit embarassing.

If anyone wants to take a look, I have this zipped up as a simple, self
contained VS2002 solution.  You can snag it from here:
http://demo.ubisense.net/InteropLeak.zip

This seems similar to the post on ".NET + ActiveX control firing many
events", but there was no resolution to that post.  Anyone have any ideas?

Rupert.