Engine Trouble

Mark Schonewille m.schonewille at economy-x-talk.com
Sat Oct 9 04:53:04 EDT 2010


Hi Cal,

Your message confused me but after reasing the other answers on this list I understood what's wrong. What you are describing is not memory leakage. It is simply a quit command badly executed. This solves the problem:

http://runrev.info/Save%20Way%20to%20a%20Quit.htm

You may need to remove the MySQL part from the script.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553

Download the Installer Maker plugin for Runtime Revolution at http://qurl.tk/ce Create installers for Mac and Windows on *every* Rev-compatible platform. No additional software needed.

On 9 okt 2010, at 05:27, Cal Horner wrote:

> Is it just me or is there a trouble with a generated engine again.
> 
> I can remember a few years (versions) ago that when an engine was created to
> drive a stack  we got memory leakage (check the windows task manager) when
> the app was closed. Simply put the stack closed but the engine stayed in
> memory.
> 
> Has that problem resurrected itself with Elsie forty-five or have I simply left out as line OS script?





More information about the Use-livecode mailing list