Quit Command corrupts standalone (stack called by standalone splash)

Richard Gaskin ambassador at fourthworld.com
Mon Feb 26 14:07:50 EST 2018

Stack file corruption is very rare with LiveCode.  It has happened now 
and then, but is rare enough (and of course serious enough) to merit 
attention by the LC team.

Even if we can mitigate the issue by altering your code, the main 
question remains:  why does a save operation become interrupted, and is 
that interruption caused by external factors or from an internal bug?

Unless you know the cause of the corruption (failing hard drive, flaky 
network with mounted network drive, use of Dropbox or other synced 
folder with unpredictable behavior, etc.) it may be helpful opening a 
bug report if only to allow the team to investigate the corrupted file 
to see if it brings their attention to something internal which may need 

  Richard Gaskin
  Fourth World Systems

More information about the Use-livecode mailing list