LiveCode Forums.

Hello,
In recent days, I try to develop some small stack to exercise myself, but LiveCode is often crashes.
I use LiveCode 5.0.2 on Mac OS X Lion.

Each time, suddenly, things do not work. Exit and restart LiveCode is not enough. I have to reboot the Mac completely.
Each time I lost several version of my work. although I saved stacks regularly to test and make a "standalone apps."
Each time, after reboot the Mac, the "recent file" of the day is lost. (not very important)

So LiveCode become unstable, it indicates that it saves out the stacks, but it does not save anything, it clears the list of "recent files", and I lost hours of work.

The last surprise was manifested by the disappearance of buttons. In fact, the buttons was already there, but, the images have disappeared from the bookstore. I had to reboot the mac as explained and I lost several versions of my work.

It is not enviseageable starting a serious project with a as unstable tool.

How can I improve the situation?

thank you in advance.

Hi Daniel.

Right now Im learning, and have made just a few stacks. Im using the Trial on Mac Lion.
Haven't run on an issue like you yet.
As you can imagine is important to me to know if this platform is stable or not, because Im planning to buy the commercial license next week.
Any other users have experiment this issue?

Are you both applying the script then saving the stack? Can you reproduce it? I'm still in Snow Leopard, as reports were that Lion was unstable.

Spencer:
I am not having problems using Lion, Im just wondering if some one else are having problems before I buy

Your experience is very unusual, there are many people using LiveCode with Lion without problems. If there is a crash you will of course lose any unsaved work, but I have never seen a saved stack lose objects, and I've never had to reboot my Mac. It's always a good idea to save your work frequently of course. If you require a reboot of the entire machine, I think something else is interfering in a big way.

It sounds like your system has incompatible software installed which RR needs to identify. All crashes should be reported to RunRev, they are top priority and are always fixed promptly. I hope you will write to support, explain the problem, and include a system crash log. It would also be helpful if you can include a short sample stack that shows the problem (don't send your working stack if it is complex, that makes it harder to diagnose.)

You might be able to find out what the problem is by looking at the system log yourself. It's in the Console app in the RunRev CrashReporter folder.

Also, if you have a recipe that consistently crashes for you, post your script here and we can look at it.