Resource DLL still active

Hi all,

We made a .Net DLL that is the managed end of an unmanaged - managed bridge. There is nothing in the DLL besides the wrappers to the unmanaged function calls and the P/Invokes. When I terminate the program the managed DLL stays active. Any ideas on why it would stay in memory Do you have to terminate a managed DLL in some way




Answer this question

Resource DLL still active

  • Deb Magsam

    Alex,

    Nope. Everything is a command-response call, no threads. I did notice that it's only when I am debugging and the debugger terminates in an abnormal fashion, like an uncaught exception. It does not seem to occur when I run the program outside of the debugger or the debugger terminates the app normally.



  • priyanka.dash

    Ah, I see. That's entirely possible. Sometimes the debugger fails to terminate the application - not much you can do

  • ozakiweb

    Are there any threads that you create Including unmanaged

  • Resource DLL still active