Rubberduck doesn't exit properly

[ghost]

When closing Excel for example, the process does not get killed which might be because still have references to COM objects somewhere. Here's an article about that problem: http://stackoverflow.com/questions/158706/how-to-properly-clean-up-excel-interop-objects.

Also it seems that the component parser tasks never get disposed of properly but I'm not sure how important that is.

[Hosch250]

@autoboosh This is our old friend the memory leak. It is because not everything is disposed correctly. When we tear it down, we need to go through and manually call Dispose() on every single item that implements IDisposable. I had this fixed for 1.4.3, but 2.0 killed almost all of that.

Here is a known list of what is not disposed:

• The menus
• The commands for the Code Explorer (a couple use components that need to be disposed)
• Perhaps the parser components

[ghost]

What about the "two dot" problem though as described here: http://stackoverflow.com/a/158752/5895299?

[Hosch250]

That may well be part of this.

[Hosch250]

Reference #1436

[retailcoder]

@autoboosh isn't the "two dot" problem only a problem when you're out-of-process?

If that's not the case, then we have TONS of Marshal.ReleaseCOMObject calls to sprinkle just about everywhere, ...and perhaps that might explain some of the intermittent crashing-on-exit.

Thoughts?

[ghost]

Oh my bad then, ignore what I just said.

[retailcoder]

@autoboosh well I hope with fingers quadruple-crossed that being in-process matters. Otherwise you could very well be correct here.

[Vogel612]

Is this still relevant to the latest releases?

[Hosch250]

Some people are still having trouble with this. Autoboosh has not been in contact with us for +/- 6 months.