Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The debugger will be your friend here. Step through the shutdown until you get stuck. That'll be the best bet.</p> <p>But... assuming for some reason the debugger is affecting the behaviour, or can't be used for some other reason:</p> <ul> <li><p>A few earlier replies suggest using FastMM. This has been the default memory manager for delphi since D2006. You can try flipping on the options to <a href="http://edn.embarcadero.com/article/33416#16ReportingMemoryLeaks" rel="nofollow noreferrer">report memory leaks</a>... but that'll only work after you've finished shutting down the process, which is what isn't working. :) So I doubt it will help you much in this case. The full version of <a href="http://sourceforge.net/projects/fastmm/" rel="nofollow noreferrer">FastMM</a>, as opposed to the standard one packaged with delphi, might have some other helpful features... But I can't recall any that would help here.</p></li> <li><p>To inspect your app while it's stuck, you could try the <a href="http://technet.microsoft.com/en-us/sysinternals/default.aspx" rel="nofollow noreferrer">sysinternals tools</a>, like Process Explorer &amp; Process Monitor. Process Monitor may show you if it's choking on any ACCESS_DENIED errors, etc, and the stack trace at the time of the error. <a href="http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx" rel="nofollow noreferrer">Process Explorer</a> could be especially useful, by listing all the handles your process is still holding open, and allowing you to view the stack of all its living threads. A familiar function or two, in the stack traces of any hung threads, may send you hunting in the right area.</p></li> </ul>
 

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