Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>This could be a DLL_PROCESS_DETACH or CoUninitialize problem. Raymond Chen's blog "The Old New Thing" has a couple of relevant articles:</p> <ul> <li><a href="http://blogs.msdn.com/b/oldnewthing/archive/2012/01/05/10253268.aspx" rel="nofollow">When DLL_PROCESS_DETACH tells you that the process is exiting, your best bet is just to return without doing anything</a></li> <li><a href="http://blogs.msdn.com/b/oldnewthing/archive/2004/05/20/135841.aspx" rel="nofollow">Do you know when your destructors run? Part 1.</a></li> <li><a href="http://blogs.msdn.com/b/oldnewthing/archive/2007/05/03/2383346.aspx" rel="nofollow">Quick overview of how processes exit on Windows XP</a></li> <li><a href="http://blogs.msdn.com/b/oldnewthing/archive/2010/01/15/9948740.aspx" rel="nofollow">How you might be loading a DLL during DLL_PROCESS_DETACH without even realizing it</a></li> <li><a href="http://blogs.msdn.com/b/oldnewthing/archive/2009/06/26/9804500.aspx" rel="nofollow">The thread that gets the DLL_PROCESS_DETACH notification is not necessarily the one that got the DLL_PROCESS_ATTACH notification</a></li> </ul> <p>As you said these are 3rd party components. You could try to make smaller test cases until the problem disappears to pinpoint the buggy component. You could also try a native code debugger and analyze what code created the error message.</p> <p><strong>The simplest solution</strong> however to work around the issue is trying to force a specific load-order of all those components. In the Main() or startup form, try to use some functionality of each 3rd party component in a fixed order. If the bug still appears, change the order until the problem vanishes. That might work.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload