Engine Trouble

Pierre Sahores psahores at free.fr
Sat Oct 9 02:25:52 EDT 2010


Try this :

on quit
	save stack <yourstack>
	wait 1
end quit



Le 9 oct. 2010 à 05:27, Cal Horner a écrit :

> 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?
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution

Pierre Sahores
mobile : (33) 6 03 95 77 70


More information about the Use-livecode mailing list