Corrupted stack
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- Posts: 641
- Joined: Tue Jul 29, 2014 12:52 am
- Location: Brazil
Corrupted stack
Hi all, not sure it there is a solution for this but I'll try, may be someone has gone throught the same problem before and has a magic solution...
I was working on a LC project when my Mac started complaining about running out of memory and I had to force power off/on
Now when I try to open the project I was working on I got this error message
and the project that originally was around 500K now it > 4G !
Where should I look for the backup file?
Any other hints?
I'd really appreciate any help in order to save me 2+ days or rework.
Regards
I was working on a LC project when my Mac started complaining about running out of memory and I had to force power off/on
Now when I try to open the project I was working on I got this error message
and the project that originally was around 500K now it > 4G !
Where should I look for the backup file?
Any other hints?
I'd really appreciate any help in order to save me 2+ days or rework.
Regards
Simon
________________________________________
To ";" or not to ";" that is the question
________________________________________
To ";" or not to ";" that is the question
-
- Livecode Opensource Backer
- Posts: 9388
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: Corrupted stack
viewtopic.php?t=3846
"If the save is interrupted for any reason (power cutoff, force-quit, etc.), the stack file may not be complete and will be regarded as corrupt, but the "~*" copy will be in the same folder -- if you see that copy, in most cases you can safely quite Rev, move the corrupted file to the trash, remove the tilde from the copied file, and re-launch Rev to get back to work with everything in place as of your last successful save."
"If the save is interrupted for any reason (power cutoff, force-quit, etc.), the stack file may not be complete and will be regarded as corrupt, but the "~*" copy will be in the same folder -- if you see that copy, in most cases you can safely quite Rev, move the corrupted file to the trash, remove the tilde from the copied file, and re-launch Rev to get back to work with everything in place as of your last successful save."
-
- Posts: 641
- Joined: Tue Jul 29, 2014 12:52 am
- Location: Brazil
Re: Corrupted stack
Thanks Richmond, bad luck there is no backup file in my folder.
I've also noticed that the "Open Recent File" menu shows me files from ages ago. So it seems something happened with LC itself...
I've also noticed that the "Open Recent File" menu shows me files from ages ago. So it seems something happened with LC itself...
Simon
________________________________________
To ";" or not to ";" that is the question
________________________________________
To ";" or not to ";" that is the question
-
- VIP Livecode Opensource Backer
- Posts: 7237
- Joined: Sat Apr 08, 2006 8:31 pm
- Location: Minneapolis MN
- Contact:
Re: Corrupted stack
What version of LC are you using? I think there were some memory leaks in one of them.
Backup files are only created during a save so there wouldn't be one after a forced quit. I'm not sure why you'd see files from an old preferences file, that's strange. If you do recreate your work, keep an eye on the file size of the stack and see if it starts growing unreasonably.
Backup files are only created during a save so there wouldn't be one after a forced quit. I'm not sure why you'd see files from an old preferences file, that's strange. If you do recreate your work, keep an eye on the file size of the stack and see if it starts growing unreasonably.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
-
- Posts: 641
- Joined: Tue Jul 29, 2014 12:52 am
- Location: Brazil
Re: Corrupted stack
Hi Jacque, I was using LC 9.6.1 when crashed. I do have LC.9.6.2 (rc 3) installed as well.
Thanks for the hint about the file size. Will take that into account
Thanks for the hint about the file size. Will take that into account
Simon
________________________________________
To ";" or not to ";" that is the question
________________________________________
To ";" or not to ";" that is the question
-
- VIP Livecode Opensource Backer
- Posts: 9842
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: Corrupted stack
Please file a bug report and make arrangements to send your stack to the team.
True stack file corruption is very rare with LiveCode, and we need to keep it that way.
Bringing this conversation to the engine team will help ensure robust quality for all.
True stack file corruption is very rare with LiveCode, and we need to keep it that way.
Bringing this conversation to the engine team will help ensure robust quality for all.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
-
- Posts: 641
- Joined: Tue Jul 29, 2014 12:52 am
- Location: Brazil
Re: Corrupted stack
@FourthWorld if you mean I should send the corrupted stack to the team I'm sorry but since it was >4GB I have deleted it!
Simon
________________________________________
To ";" or not to ";" that is the question
________________________________________
To ";" or not to ";" that is the question