On 15-May-07, at 10:28 AM, John Balestrieri wrote: > Yes, it helps. This is because AppleScript leaks. A lot. > > <http://www.realsoftware.com/feedback/viewreport.php? > reportid=cuosmfjm> > > You'll get this leak with MBS and by including your AppleScripts in > your project. It's not MBS's or REALSoftware's fault, it's Apple's. > Even an compiled AppleScript application that remains open (with an > idle handler) will leak memory as it executes tell blocks -- it's > very noticeable after a few hours on one AS process I have running at > work. > > If you are running scripts hundreds of times (as I do at work with > the automation server I've written) you leak tons of memory. When you > run the script through the shell, all AS leaks are cleaned up when > the shell terminates. > > By running through a shell, you also have the ability to watch the > script running by running an async shell. That also means you can > terminate it whenever you want -- otherwise, when you run the script > through other means (i.e., internally from Rb) your app is at the > mercy of the script completing or timing out.
I dont tend to use a lot of AS in my apps so I'd never noticed this If running through osascript makes it work better (ie/ cleans up the leaks) then that's good Still doesn't integrate as nicely but that's not that hard to work around if I wrap a RB method around a call to osascript in a synchronous shell Any downsides (encoded text , passing paramaters, etc ) that you've encountered ? _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
