Comment 1 for bug 962333

This was fixed in revision 1350. I just verified this from trunk at rev 1352 by starting a test run, quitting half way through restarting and letting it sit for a full 5 minutes before clicking recover. It happily recovered and went on.