I noticed a similar bug just recently. The case I saw was it searched 93% of the database and only found one hit near the 1% mark. It started the next search right after that hit even though it had already searched 92% of the database after that. But since the second batch found no hits, the bug didn't recur and the third time it just searched the small remainder of the database.

Perhaps you saw this case rather than what you reported (since holli and I haven't been able to reproduce it)? But I'll look for cases that don't set the point to search next correctly besides the one I recently identified but haven't had a chance to fix yet.