[Brian]

A bit more detail on what is happening:

First, it's important to know that the bug will not cause any data loss. The problem affects a cached copy of the information in the database, but it doesn't touch the underlying transaction files that cache is built from.

The bug happens when two normal parts of an OmniFocus launch both try to write to the cache at the exact same time. If the writes both happen at different times there's no problem; it's only when they overlap that the cache gets into a bad state.

The bug becomes more likely to trigger during a launch where a lot of start or due dates have passed since the last time OmniFocus ran. This is because one of the two things I referred to above is the "catch up with everything that happened while OmniFocus wasn't running" process is one of the two things I referred to before.

If it's been a long time since the last launch, or if there are more dates attached to actions in the database, there's a relatively larger chance of being affected by this.

Again, we're really sorry for the trouble this is causing!