where did 'saved a crashed version' go apple???

If you simply change your workflow to include saving after each important addition/change you will not lose any more work. I have save as a one key command (F5) and I hit it all the time.

AFAICT, Logic still saves crashed sessions.

Saves crashes for me, but I press option S all the time also (which is also handy for the other midi muting thread, because it means that when you revert to saved to get round that, that you keep all your most recent changes).

Sometimes it saves a crashed version, sometimes not. Sometimes Logic locks up with spinning beachball of death and has to be force quit (yesterday force quit didn't even work and I had to reboot my machine from the power button).

It makes sense to save as often as you can but unfortunately some big sessions take many seconds to save so it's not practical to save as often as I would like to.

I also had a situation recently where I was hitting the save command but Logic wasn't actually saving the file. Would have been a disaster with hours of work lost but fortunately it was saving the project file backups so the latest version of that had everything. Bizarre.

Mike Connelly wrote:
Sometimes it saves a crashed version, sometimes not. Sometimes Logic locks up with spinning beachball of death and has to be force quit (yesterday force quit didn't even work and I had to reboot my machine from the power button).

Came across this and thought of this thread (thanks to: Logic Dudes http://logic.dudesnetwork.com/ ;

Force Project Save on Application Hang
by Matt on February 7th, 2010 in Advanced
Application crashes are inevitable. They will happen at one time or other and seem to strike at the most inconvenient of times. DAW apps can crash from bugs in their code or from bugs or issues with third party plugins. Sometimes, Logic is smart enough to detect a crash and save the current project as a “Project (crashed).logic” file. However, I have had Logic lock up but never completely crash on more than one occasion.

This happened to me today while working on a project. I tried to change to a screenset with a 3rd party plugin window open while the project was looping. Something caused Logic to lock up and display the spinning beach ball of death while the project continued to loop in the background. I couldn’t stop playback, change screensets, or save the project. I figured Logic would eventually crash and ask me to save, but 5 minutes later it was still going and I still couldn’t do anything. I looked at the timestamp of my project file to see when I last saved. Intstead of losing my last 10 minutes of work, I decided to figure out a way to make Logic crash and automatically dump the project. Simply selecting “Force Quit” was not an option because it doesn’t tell Logic to dump the project before quitting. After some quick testing on another machine, I found out that if you kill Logic via the terminal it will save the file as if it crashed as long as you send the correct kill signal.

Please note that this may not work in all situations.

Here’s how to do it.

Open Terminal.
Type ‘top’ and press enter. You will see a window like the one below.

Find the PID for Logic. In the screenshot above the PID is 8070. This number will change each time you launch Logic.
Press ‘q’ to get out of top.
Type the following command and press enter. Remember to replace XXXX with the correct PID.
kill -s ABRT XXXX

Logic should tell you that it crashed and has saved the project for you.

Hopefully, you can proceed to reopen Logic and load the (crashed).logic project file and hopefully recover your changes without Logic crashing again.
Performing the steps above will cause Logic to save a (crashed).logic project file even if it is not locked up. So, feel free to try it on an empty project for practice. That way you don’t mess it up if you have to use it on an important project!