try n use marshal.releasecomobject to release the objects having ref. to
explorer/inspectors etc.
and then gc.collect

"Oliver Giesen" wrote:

Oliver Giesen wrote:

The symptoms of the breakage are sudden exits or hangs on certain
operations.

Some more bits of information that might (or might not) be useful:

* In the case of the sudden exits, my addin receives no BeginShutdown
or Disconnection events (_IDTExtensibility2) nor a Quit event from the
application object nor do the various explorers or inspectors trigger
any Close events but code in unit finalization sections apparently
still gets called alright.

* A new suspicion: I discovered that I can also trigger the crash by
repeating certain operations several times, e.g. opening and closing a
dialog that is part of my addin four times. Looks like a memory issue
to me. However, I have already used various mem checking tools and
there appear to be no leaks. I'm also using the FastMM replacement
memory manager which can be run in debug mode and it's also not
reporting any memory management issues...

any more ideas?


Cheers,

Oliver