What causes the recover.log to get created?

Discussion created by dhrowe on Nov 19, 2014
Latest reply on Nov 20, 2014 by gdurniak

I have a test machine on 10.10 - to test ;-)


I had a file I am pretty sure I had to do a force quit in Yosemite on some test files but when I opened them again to see what would happen, no recover log was created.


I also looked using FMDif 3.0.7 and it does not show a force quit warning.....


So then I tried it again on a bigger solution and in 10.9 I get a recover log after I force quit, but so far I have done it several times on 10.10 and no log so far. So are they being closed correctly with a force quit or is this an ugly bug?