Outlook Add in + memory

[Selva kumar]

Hi,

I created a addin for Outlook using VSTO 2005. The Program,
Installation is fine. One of our customers has reported that installing the
Addin holds the email sent in the Outbox for some time. He also informed,
uninstalling the Addin reverts the problem. Based on this information, I
checked in my development environment and found, the memory creeps up to 130
M when I use the Addin which is 30M when the addin is not installed.

So I created a new addin with only one command button that alerts a
message when clicked. This goes to 70M. The main factor is, if the add in is
installed, clicking on the emails, read write, creeps the memory going on,
even no code is executed from the Add in. It may be caused by
AddinLoader.dll.

If the Outlook is minimised, the memory comes to 2M. Why is this huge
variance?

Is this a issue or I am missing something.

Regards

Selva kumar

 

[Ken Slovak - [MVP - Outlook]]

Outlook does use more memory as it runs and takes memory as needed. It does
release some of that memory when it is minimized. That's normal.

If it uses a lot more memory with your addin running and doesn't release
that memory or the memory usage expands way beyond normal with the addin
running as opposed to when it's not running then I'd suspect a memory leak
in your code.

Are you releasing all your COM objects as they are no longer needed? Are you
calling Marshal.ReleaseComObject() on those objects before setting them to
null as appropriate when those objects aren't needed any longer and the
RCW's for those objects aren't needed any longer?

 

[Selva kumar]

HI,

I created addin using the Visual Studio Tools for Office and it is a managed
code. I have placed the code in

http://social.msdn.microsoft.com/Forums/en-US/vsto/thread/bee7e45e-1b2a-4b65-b6b0-015228516f49

Is it possible to use the Marshal.ReleaseComObject() in my code. I tried
the GC.collect() and it releases the app domain memory and not the
AddinLoader memory.

Thanks

Selva kumar

 

[Ken Slovak - [MVP - Outlook]]

You certainly can use ReleaseComObject() but that will only release your own
object variables and in the VSTO created AppDomain.