I saw it too.
But think it’s Applescript that’s having memory issues, since the memory pressure only drops when Applescript is quit
Hello
Say you turn your AppleScript into an app, which you let die after 23 hours, and then starts the same app some 30 minutes later from Calendar for instance? You’d have to keep check on the item number of the file, you’ll start to process, by saving it before killing the app, and reading that number back in upon restart. (Or start with file number 1 if no file with next file number is written so far.
Hi McUsrII,
sounds interesting, working with the Calendar app, although a little cumbersome: it would be handy to easily start and stop the process, since I have to work on the computer from time to time. So a relative rather than absolute time should be used. But I have the right direction now: restarting the app seems to be the next thing I should try.
Thank you!