This macro checks for a particular open window. If it finds it, it does a Save operation (Ctrl-S). It waits for 5 minutes, then loops back and repeats the check and the Save, running until it is manually stopped. The RAM used by this macro increases a little after some but not all loops. Also, the amount of RAM used by the macro when it first starts up varies from 3 MB to 8 MB. It is a compiled macro using Macro Scheduler's excellent feature, Create Exe, and is being run from the executable. The Macro Scheduler application itself is not running when this compiled macro is running.
Is this to be expected? Is there some way to keep RAM use from increasing? Thanks.
