Save stacks periodically to avoid crashes?

simplsol at simplsol at
Fri Mar 24 12:02:31 EST 2006

This has been my experience exactly!
The more I save the less Rev crashes. It has been a hard lesson to 
learn - especially coming from a HyperCard background where one never 
needed to save.
As for 2.7, I tried it for two days and found it to be full of problems 
- went back to 2.6.1, which has been (for me) the only semi-stabile 
version of Rev yet. I really wish they had done a 2.6.2 instead of the 
current 2.7!
Good luck.
Paul Looney

-----Original Message-----
From: Jon Seymour <jonseymour at>
To: use-revolution at
Sent: Fri, 24 Mar 2006 10:49:26 -0600
Subject: Save stacks periodically to avoid crashes?

    Hi, I've been using Rev for about a year. I'm sure it won't shock 
most of you to hear that periodically Rev just seems tired and crashes. 
Now I am sure that coding glitches are sometimes at fault, but 
generally speaking I think Rev (esp. 2.7) has stability issues. Here's 
the thing, though: it seems that if I am saving the stack periodically, 
which I would tend to do to avoid losing data in a crash, the program 
actually crashes less. It's as if saving has some benefit to memory 
management or who-knows-what-else in the engine. It's like a "refresh" 
function. Has anyone else observed this? Is there a rationale? Would it 
be smart to have a commercial application save its stacks regularly, 
not only to store user changes, but simply to confer stability? 
 use-revolution mailing list 
 use-revolution at 
  Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences: 


More information about the Use-livecode mailing list