"Updating database..." bug reason

[TeToTa]

I'm not the only one facing this annoying bug:
viewtopic.php?p=51481
viewtopic.php?p=44276

The reason is the follow: it fails to read NTFS data (I assume) when hard drivers are stopped.

I have the enabled "hard drive stopping after N minutes of idle" in Windows' power setting (to make the computer quiet).

So, I need manually to open any file on each hard drive to bypass "Updating database..." stuck.

This bug is Everything only. Any other program usually starts hard driver itself (if it's required for the program work) if the hard driver was stopped.

[void]

Thank you for the issue report TeToTa,



The "Updating database..." status is shown when Everything updates the database for the first time since starting.
It can take a long time to update the database if there is many changes to your disk.



This issue can be caused by Everything being unable to save its database to disk.

Please make sure Everything is installed correctly and running as a standard user:

• In Everything, from the Tools menu, click Options.
• Click the General tab on the left.
• Check Store settings and data in %APPDATA%\Everything.
• Uncheck Run as administrator.
• Check Everything Service. (Please make sure this is tick-checked and not square-checked)
• Click OK.
• Exit Everything (right click the Everything tray icon and click Exit).
• Restart Everything.

This issue can be caused by stuck Windows updates.
Please make sure there's no pending Windows updates.



Please check for any programs that might be spamming your file systems.
Sort by date modified to see recently changed files.



Is Everything always reporting "Updating database..." until you access your drive that is asleep from another program?



Please try the Everything 1.5 alpha as the updating is now done in the background allowing you to search immediately.

[TeToTa]

I have already seen this message in other topics.

I wrote the real reason of the bug.

It stucks forever with "Updating database..." message until I open any file (or folder) on a stopped hard drive from File Explorer or with any other program to start spinning of the hard drive.

1.4.1.1005.x64

First I will try:

Code: Select all

/folder_update_rescan_asap=0

Possibly, it should help too.
viewtopic.php?p=55562

[void]

Could you please send some debug logs.

In Everything, type in the following search and press ENTER:
/debug_log
Close the debug console to terminate Everything.

From a command prompt, navigate to your Everything.exe location:
For example:
cd "c:\program files\Everything"
Run Everything with the -debug-log command line option:
Everything.exe -debug-log
Let Everything sit for 5 minutes.
This should give enough time to capture any errors.


To stop debug logging:
In Everything, type in the following search and press ENTER:
/restart



Could you please send your %TEMP%\Everything Debug Log.txt to support@voidtools.com
This will help identify the issue so I can work on a fix.

[TeToTa]

Or maybe my suggestion is wrong and these were just coincidences.

For example, I started Everything now and just waited. "Updating database..." was 1:50 seconds.
2 minutes of "Updating database...". So, it looked really like a freeze.
No progress, only the static "Updating database..." text.

I will try to reproduce the "freeze" is longer than 5 minutes.
However, it seems for me that with the spinned hard drives it loads always notable faster, but it may be just a feeling.

[TeToTa]

The real reason is incredibly slow reading of NTFS journal (when enabled Windows search indexing thing). It very slow "updates database".
For example, opening of Everything 1.4 takes 7+ minutes after renaming of a folder with 190k files.

How to reproduce:
- Open then close Everything 1.4 to check how it opens,
- Create an "indexed_folder" folder,
- Add this "indexed_folder" to the Windows search index ("Indexing Options" -> "Modify"),
- Create a folder "a" within "indexed_folder" and put 200k of files into it,
- Await until Indexing Options is complied indexing,
- Open Everything 1.4 ...it will take minutes for "Updating database...",
- Close Everything 1.4 after it is ready,
- Rename the "a" folder to "b",
- Await until Indexing Options is complied indexing,
- Open Everything 1.4 ...again, it will take minutes to be ready.

For me, it takes 7+ minutes, I tested it multiple times. However, the first time I tested it, it took even 20 minutes!

In comparison, Everything 1.5 "alpha version" is ready in 5 seconds!


---

UPD.
Using of Windows search index is not required. 1.4 slow opens even without it, when I rename (or move) a folder with a lot of sub content.
The same 7 minutes.

[therube]

- Add this "indexed_folder" to the Windows search index ("Indexing Options" -> "Modify"),

Is that required to see the issue?
(Or is it also seen when not doing that?)

- Await until Indexing Options is complied indexing

So this is (again) "Window search index" that we're talking about here?
(So that would seem that the answer to my first question is, yes, the "Windows search index" part is required.)

[void]

Renaming a large folder is slow in Everything.

All subfolders and files need to be re-inserted into the database to maintain sorting.

[TeToTa]

Due to this bug 1.4 looks more like an alpha version than 1.5.

This bug is very annoying. It spoils the impression of Everything.

I think you should rename 1.5 "Alpha" to 1.5 "Beta".
An alpha software is usually a very raw software, that should not be used by consumers.

I don't know why you still not released 1.5, but it feels much better than 1.4.