I'd like to raise this again as I have a following question, and the issue is consuming quite a lot of time for us which I'd like to reduce if at all possible.
We have pretty huge data sets that we need to search, with deep directory structures. If a corrupt file is encountered on a search, the behaviour is normally as exhibited above. Usually you can make out roughly where the file causing the problem is located from the status bar at the bottom of the screen, however if it's buried deep within a structure then it's very difficult to narrow down.
Is there a better way to see which file is currently being searched?
Once the file is identified, we can remove it an rerun the search, usually successfully.
Thanks for your help,