Comment 2 for bug 731752

On Wed, Mar 9, 2011 at 9:09 PM, Uday Reddy <email address hidden> wrote:

> 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.
>
>
OK, I'll try to debug it further when i get time.

Some additional things to note

1. This occurs on larger folders which have never been visited before. I
guess this would indicate it is a problem with the initial build of the
threads database (assuming each folder thread db is independent).

2. It seems to happen with all slightly larger folders, so while it still
may be some message which is 'unusual' or has something that the code cannot
handle, this seems less likely.

3. In all the cases I've run into this, no other operations have occured in
that folder i.e. not visited it, done something and then visited it again. I
don't seem to see this problem with smaller folders, but don't know yet if
there is a 'cut-off' size where this begins to occur.

Tim