Ok so this is kind of a Seaside Question, but also kind of a Newb question. I'm going to ask it here because I think it's mostly a newbie problem.
I created a seaside app, that seemed to hang the smalltalk process. When I hit the URL the page never rendered, and the image seemed to freeze up.
In fact it brought my Mac pretty much to it's knees. I assume some kind of infinite loop sucked up all the swap space.
Subsequent restarts of the image showed the same behavior.
In the end I seem to have ended up corrupting my image, by forcing a quit in the middle of a save that was taking forever.
So now when I try to restart my Squeak/Seaside image, I get the message:
Read failed or premature end of Image file.
after that image, the Squeak process crashes.
I think I'm kind of in a bad place. I've done development over the course of several days. Have I lost all that work? Is there any kind of journal file that might have changes to the image? How badly am I toasted when my image goes south like this? Should I be making copies of the image as an additional protection strategy?
Tony Giaccone
On Sat, Nov 22, 2008 at 07:35:36AM -0500, Tony Giaccone wrote:
Ok so this is kind of a Seaside Question, but also kind of a Newb question. I'm going to ask it here because I think it's mostly a newbie problem.
I created a seaside app, that seemed to hang the smalltalk process. When I hit the URL the page never rendered, and the image seemed to freeze up.
In fact it brought my Mac pretty much to it's knees. I assume some kind of infinite loop sucked up all the swap space.
Subsequent restarts of the image showed the same behavior.
In the end I seem to have ended up corrupting my image, by forcing a quit in the middle of a save that was taking forever.
So now when I try to restart my Squeak/Seaside image, I get the message:
Read failed or premature end of Image file.
after that image, the Squeak process crashes.
I think I'm kind of in a bad place. I've done development over the course of several days. Have I lost all that work? Is there any kind of journal file that might have changes to the image? How badly am I toasted when my image goes south like this? Should I be making copies of the image as an additional protection strategy?
All the code changes are stored in the .changes file sitting next to the image. You should be keeping your source code in a Monticello repository as both a backup measure and a code sharing measure. And yes, you should make copies of your image. It's as easy as World > save as new version.
On Sat, Nov 22, 2008 at 08:52:46AM -0700, Matthew Fulmer wrote:
All the code changes are stored in the .changes file sitting next to the image.
To recover your code from the .changes file, open a new image, and either drag the old .changes file onto the squeak desktop, or find it in world > open > file list. Invoking "recent changes" on the changes file will lead you to a tool that allows you to selectively file in your logged code
On Sat, Nov 22, 2008 at 07:35:36AM -0500, Tony Giaccone wrote:
I think I'm kind of in a bad place. I've done development over the course of several days. Have I lost all that work? Is there any kind of journal file that might have changes to the image? How badly am I toasted when my image goes south like this?
No worries, see the "How can I recover my work if a crash has occurred" explanation here:
http://wiki.squeak.org/squeak/2168
Should I be making copies of the image as an additional protection strategy?
Yes, it is a good idea to do that once in a while.
Dave
beginners@lists.squeakfoundation.org
-
David T. Lewis -
Matthew Fulmer -
Tony Giaccone