Comment 1 for bug 731752

Hi Tim, note that your backtrace has gotten cut off.

The problem is that the threads database is getting corrupted or bcoming faulty somehow. This is an integrity check running and throwing up an alarm.

For the time being, you can type `c' (for continue) when this happens, and it will try to rebuild the threads database. There is no guarantee that the rebuilt database will not be faulty again. If the problem happened because of some previous operations then the rebuilt database will be fine.

But, if it is some pattern in the folder that is causing the fault then it might happen persistently. The only way out at the moment is to revisit the folder afresh without threading.