Damaged dbs when killing app in debugger

[jda]

>  > With this FC release I've found that if I quit my app while it's in
>>  the debugger (Command-K) I can often corrupt databases. This happens
>>  even when I'm not adding or deleting references, just doing searches
>>  and the like. This didn't happen in previous releases -- maybe due to
>>  the new cached data? Anyway, here's an example of a crash log when I
>>  try to open one of these databases:
>
>Yes, looks as something is not flushed.
>
>Please keep eye:
>
>     after flush -- if stop debugger -- does db corrupts.
>
>After flush it never should
>

Yes, that's why I said I had not modified any data. So no need to 
flush (I am pretty careful about flushing whenever any data is 
added/deleted)...

Jon