Contrary to urban legend there is no way to hack an AEP file to repair it. It's botched and that's the end of it. That's why it's a good idea to get into the fine art of file versioning, incremental saves and backups...
But how are we sure that the file itself is actually damaged? I don't understand anything of this crash logs but does it say anyting about a damaged / currupt file?
Thanks for the reply.
First of all, DON'T KILL YOURSELF! Suicide is a permanent (wrong) answer to a temporary problem.
There is a way to translate an AE project into a human-readable text file. It's called Open Sesame. That might allow you to have a peek around and maybe change a few things.
Definitely file a bug report and include the project for them to look at.
Do you have any earlier versions of the project saved? Do they work? (If you don't have any, you might consider incremental saving on your next project.
Yes you are right about the first point.
Unfortunately Open Sesame won't work because I need to open the file first in AE and that is not happening anytime soon.
Thanks for the reply though.