Like Peter said, there's the CMD-. shortcut to break infinite loops.

And if that doesn't work and the image crashes, you still typically don't lose a lot of work. Don't forget, that every time you save (accept) a single method, that change is written to the .changes file. Even if you haven't saved the image before it crashes, you can use the��

'World > Tools... > Recover lost changes' tool to recover a lot of your work. (Since you've been contributing to the UPBE book, take a look at the 'How to get your code back' section in the Environment chapter :) ).

On Thu, Apr 16, 2015 at 7:58 PM, Peter Uhn��k <i.uhnak@gmail.com> wrote:

There is a shortcut "alt + . (dot)" (maybe ctrl/cmd depending on platform), that will break the current execution and show the debugger (which you can then close) - useful if you have infinite loops and so forth.

Peter

On Fri, Apr 17, 2015 at 1:51 AM, Gaurav Singh <grvanm.coder@gmail.com> wrote:
Is there any way to get back the Pharo image working when it freezes without closing the Pharo image because many times the work isn't saved and then it costs a lot restarting the pharo image?