Beta 1.5.0.1412b, re-indexing despites having that big database copied over?

[abr01]

I have copied that big database with 2.7GB to the proper place, but indexing started anyway, taking ages. Isn't the database supposed to prevent the re-indexing?

Apart from that, nice to have 1.5.0 in Beta now!

[void]

Everything 1.5b shouldn't be reindexing.

What is shown under Tools -> Debug -> Statistics -> Build -> Last rebuild reason?

Could you please send your Help -> Troubleshooting information -> database location



Everything 1.5b might be using an old Everything 1.4 database.
Please terminate Everything and manually copy your Everything-1.5a.db to Everything.db, then restart Everything.

[abr01]

For Last Rebuild it shows "Remove NTFS volume".

That sounds reasonable, as i found drive D: to be included, which i want to avoid. I have two backup disks, that would be D:, and redundant to my main disk, so i figured that hwvaing two slightly different D: drives is maybe not a good idea. So i had D: removed.

And regarding the other thing, i believe it did it correctly, having moved Everything-1.5a.db to the according %localappdata% folder. Anyway, Everything is at 60% now, so might better leavit run rhrough now.

Thank you!

[abr01]

Now i will stop the whole process, delete that old database, and start from scratch.

Here is what happened: after the indexing was finally 91%, and i was away from the keyboard for a minute, i came back to see the Everything window has vanished. My shortcut to bring up the main window didn't work, so the program was terminated anyhow.

Starting it again, it was again back to 40%!

Now it's crawling around 53%, but i'm afraid, the same will happen again, like a indexing loop. Given, that i try to build the index for almost 11 hours now, i have to break it up. Hoping, that i don't have to go back to 1.5 alpha.



Edit: after deleting the unfinished new index, and all the old .bak version, i got some content now, which looks decent, and no re-indexing started so far. Which might be a good sign. But the file coun't is down from around 1.4 million files to under 700.000.

But maybe it's due to the fact, that i had the D: drive excluded. It was not plugged in all the time, but maybe those mayne ghosted offline files contributed to the bigger file count.

[Murky3904]

Here is what happened: after the indexing was finally 91%, and i was away from the keyboard for a minute, i came back to see the Everything window has vanished. My shortcut to bring up the main window didn't work, so the program was terminated anyhow.

Interestingly, the same thing is happening to me on v1413b. Event though I have tried deleting all old database files and backups and started afresh. Launching the app after the silent crash resumes the indexing from around 74% for me though.

1.5a worked excellently. I hope a new version comes out soon and fixes this issue.

For void:

• My Database location is the default one (%LocalAppData%\Everything\Everything.db)

• The Last rebuild reason is "Unable to open database file". It is an old status though. I deleted old database file(s) since then. Each time after that Everything has been working on the .db file that invariably stays at 968 MB.

Edit:
I ran

Code: Select all

perfmon /rel

and found multiple instances errors such as this:

Problem
Stopped working

Description
Faulting application name: Everything.exe, version: 1.5.0.1413, time stamp: 0x6a0be2c6
Faulting module name: ucrtbase.dll, version: 10.0.26100.8328, time stamp: 0x3e0a6430
Exception code: 0xc0000409
Fault offset: 0x00000000000a4aee
Faulting process id: 0x6C80
Faulting application start time: 0x1DCECEF1FC33166
Faulting application path: C:\Program Files\Everything\Everything.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: b62d70d9-48bf-419f-a35a-d6245ca911e8
Faulting package full name:
Faulting package-relative application ID:

[void]

Thank you for the issue report Murky3904,

Everything doesn't call ucrtbase directly.
This is most likely an iFilter/property-handler crashing and blowing up the stack.

What properties are you indexing? (Help -> Troubleshooting information -> properties)
Are you indexing content?