If an uncaught runtime error occurs, or you interrupt execution, when your script still has certain links to the outside world in an open state, Script Debugger helps out by giving you the chance to close them. There are two primary situations:

• Your script has left a file open (using the open for access command).

• Your script is in the middle of a transaction (talking to FileMaker Pro, the only application that implements transactions) and has left the transaction open.

In a case like this, Script Debugger will show its Leaks dialog.

In the above illustration, the dialog shows a list of files that have been left open (there happens to be just one). Typically, you should click the Close All button. This closes all open files.

Alternatively, you could select a file and click the Forget button. This means to leave the file open (basically you’re telling Script Debugger not to help out here), but that isn’t something you’re likely to want to do, since the leak then remains.

In the case of a transaction, you can close the transaction to “commit” it, or click Abort to “roll back” the transaction.

The Leaks dialog can be summoned any time open resources exist, by choosing Script > Show Leaks. (You can also add a Leaks button to the script window’s toolbar.)