LiveCode Forums.

Hi, I'm upgrading from LiveCode version 5.5.4 to 6.1.2. I consistently get a crash when I try to save a stack. The stack file "testing.rev" which is 4.5mb in size is them reduced to 1.6mb in size and a duplicate is made with the '~' at the end ('testing.rev~'). My instinct tells me the errors is in the revFrontScripts button of the front scripts. The same thing occurred when I tried to upgrade to the last couple of stable releases so I usually just go back to 5.5.4, but this time I'd like to stick with the new version. Any ideas? Joseph

I haven't seen the problem here, but LiveCode should never crash so this deserves a bug report (you can submit it here: http://quality.runrev.com ). You'll need to include a copy of the crasher stack so the team can fix it.

Thanks Jacque. I'll probably have to go that route, but first I'll investigate a little deeper. Joseph

Well, one common cause of crashes, especially in old stacks, are imported images that somehow got corrupted. If you have a lot of images in the stack you could try deleting them from a copy of the stack and opening that copy in 6.1.2, just as a test, so you know if that's the cause.

I'm now having the same problem since I upgraded from 5.5.1 to 6.5. And it crashes on QUIT too and says my stack is corrupted.

Hi Thomthib,

As Jacque has mentioned, LiveCode should never crash so please submit a bug report to our Quality Control Team and we should be able to look into this further.

Kind Regards,


Neil Roger
--
RunRev Support Team ~ http://www.runrev.com
——

I have found out what was causing my stack to crash although I don't understand why. The stack didn't crash with LC 5.5.1 but with all versions of LC 6x it did.

A GIF image was somehow causing the program to crash. Once I removed it, the stack didn't crash anymore. I've saved and quit several times now with no crashing. This is how I found the problem:

1. Using LC 6.6.1, I tried reconstructing the stack from scratch by copying objects from the original stack into a brand new stack. As long as I didn't save or quit the original stack I could use it as a source for copying objects into a new stack.

2. First I opened a copy of the original stack (the one that always crashed on QUIT or SAVE).

3. Then I opened a brand new mainstack.

4. In the Application Browser I sorted the objects in the original stack by layer from lowest to highest.

5. I used the Application Browser to copy and paste a few objects at a time from the original stack into the new stack.

6. I copied several groups of objects and all went well, but then I copied a group of 5 or six objects, and the program crashed with the same error window that appeared before during other crashes.

7. I trashed the stacks that I was working with and started the process over again and found that the stack crashed whenever I tried to copy and paste objects in the same layer group.

8. I then started over again until I was able to narrow it down to the object that was causing the crash. It was a GIF image that I wasn't even using anymore.

9. I deleted the image and there hasn't been any crash since. I am so happy and relieved to have found the problem, but I don't understand why an image which isn't even being used would cause this problem.

This confirms what Jacque wrote on 22 Oct 13.