I have an applescript that is called by Filemaker. The Applescript calls serveral other scripts, located on a Google Drive to load those scripts, and then calls subfunctiona of those scripts.
Recently, another user of the script on a different unit, has experienced stalls at one point in the script.
Is it possible that the command to load another applescript, and running that applescript that then calls Microsoft Word, burdens Applescript’s memory and hence might be a cause of the main Applescript stalling?
If so, would setting the variable that identifies the loaded Applescript to missing value release some of that memory?
In the event that you reach AppleScript’s memory cap I would expect a crash with a clear error report rather than a stall.
Yes. Setting a variable that contains a loaded script to missing value will reduce memory usage. But if you hit the cap there’s no recovering so I don’t expect that this is part of a solution to your condition.
I would look at inserting temp code for confirming the library scripts are being properly loaded, and that calls to them are successful. Remove or modify error handling to reveal the point at which the main script becomes unresponsive. Temporarily add dialogs to mark crucial steps etc. Good luck with your spelunking!