[KinoSearch] Index optimize failure

[Henka]

Quoting "Marvin Humphrey" <marvin at rectangular.com>:
> Do you recall the last time you updated before r3875?  r3875 itself  
> is definitely not the culprit -- it's a one-line fix for a memory  
> leak in a testing-only file.
>
> I know you watch the commits list for stuff like this, but did r3737  
> from a month ago slip by?
>
>   ------------------------------------------------------------------------
>   r3737 | creamyg | 2008-08-19 12:53:41 -0700 (Tue, 19 Aug 2008) | 3 lines
>
>   Change field numbers to start at 1 instead of 0.  This is a
>   backwards-incompatible index format change.

Nah, I remember noting this commit.

I seem to recall doing an update about a week or two ago, followed by  
an index run over a few days to build the test indexes.

Might be a good idea to reindex the subs in question and re-merge and  
see what happens.

> Will you be able to recreate the circumstances that led to this bug,  
> even if we can't condense a test case?  Meaning, can you duplicate  
> the sequence of subindex creation and merging?

Yes.  You'll recall I do a lot of logging... I can recreate the  
sequence of events exactly.

In fact, that's what I'll start tomorrow and let you know how it goes.

I'll also see about triggering that breakpoint and doing a bt before  
rerunning everything for that particular master index.

Cheers
Henry



_______________________________________________
KinoSearch mailing list
KinoSearch at rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch