UI Hangs...

[Shooter3k]

I realize I'm likely the exception as most people do not have 40+ drives connected to their machine....

I experience the UI hanging very often. I'm wondering what I can do to avoid this in the future....

Times when the UI hangs that I can think of right now:
1. when I start the machine, Everything is usually not usable for the first 10-20 or so minutes
2. Whenever I add/remove folders from the Options/Indexes/Folders list, it basically always causes the entire UI to hang for a very long time. It might be 5 minutes, it might be 30 minutes, it might be 4 hours. Once it's no longer hanging, it will sit in a state that it cannot be used, like "scanning xyz" or "building folder hierarchy" or something similar, and while it's in those states, the UI is usually hung as well.
3. if I add/remove drives and it thinks it needs to calculate if it needs to rescan something
4. when it decides it needs to rescan something

Thoughts:
1. How can I stop this from happening? My preference is that it would use 100% cpu/ram/disk whatever it needs to do in order to catch up but still be usable and not hang.
2. I'm willing to do whatever necessary to be able to avoid the UI hanging. Is there some kind of debug mode I can run it in for a month and send it to you?
3. can I give the application more priority or resources or something so it doesn't starve itself for resources and hang the UI


Any advice is appreciated

[therube]

Help | Troubleshooting, might help
Tools | Debug -> Statistics, might help

Are you indexing Properties?
Are all the drives local? On a NAS or similar? Might sleep be playing in?

[Herkules97]

I realize I'm likely the exception as most people do not have 40+ drives connected to their machine....

I experience the UI hanging very often. I'm wondering what I can do to avoid this in the future....

Times when the UI hangs that I can think of right now:
1. when I start the machine, Everything is usually not usable for the first 10-20 or so minutes

I index 34 devices on one instance without any major issues(Of which 16 are online currently and has been for a few months at least, so if you mean 40+ ONLINE then I'm far from that ). Across these devices, it's 47.9mil folders, 132.6mil files.
Closest would be one of the devices that go to sleep often and so when I restart the instance, it takes a minute on the reading journal part because it is starting up that one HDD.
Or when a different device is a bit slower than usual and also causes it to be a bit slow. But no UI hanging, just slow retroactive journal reading.
But besides these 2 HDDs I don't have much issue.

2. Whenever I add/remove folders from the Options/Indexes/Folders list, it basically always causes the entire UI to hang for a very long time. It might be 5 minutes, it might be 30 minutes, it might be 4 hours. Once it's no longer hanging, it will sit in a state that it cannot be used, like "scanning xyz" or "building folder hierarchy" or something similar, and while it's in those states, the UI is usually hung as well.
3. if I add/remove drives and it thinks it needs to calculate if it needs to rescan something
4. when it decides it needs to rescan something

This is a necessary part at least AFAIK, when you add folders it has to rebuild the entire thing. This requires about double the RAM at the peak of the stages so make sure you have the RAM, otherwise it will presumably crash something..Probably including the instance itself but in my experience some background system thing usually crashes, if nothing else crashes, when hitting 100% commit. Not much of an issue if you restart your system often, though I only do it once a month or whatever. Most recent 2 restarts have been system crashes, I think..So I don't even restart the system normally most of the time.

I've had the EBV window not responding from adding new folders, though I think maybe in newer versions like 1.5.1386a and such it isn't as common? Not sure. Either way it's still doing the same stuff, just don't bother it and it'll eventually finish..Presuming there isn't a bug and it isn't actually doing anything.

For me the time it takes to rebuild is about 1h6min via the last time in the stats page, though this was without adding any folders. I restarted it while a lot of files were being made and deleted so it was outdated by the time it finished restarting fully. There might be ways to prevent this, maybe by increasing the USN journal size but I haven't touched that stuff.

Thoughts:
1. How can I stop this from happening? My preference is that it would use 100% cpu/ram/disk whatever it needs to do in order to catch up but still be usable and not hang.
2. I'm willing to do whatever necessary to be able to avoid the UI hanging. Is there some kind of debug mode I can run it in for a month and send it to you?
3. can I give the application more priority or resources or something so it doesn't starve itself for resources and hang the UI

1. Don't know.

2. You can start by making the instance 1.5.0.1423b if not already, then Tools - Debug - Verbose, then same menu Start Debug Logging BEFORE any hanging. Then Stop Debug Logging when it's done freezing for the moment.
Warning, that this can potentially take 1MB per 5 seconds or so..If it freezes for a few hours it could either end up being GBs or potentially MBs if it never logs anything while frozen. But if it's the same hanging that I've had, it's still working in the background so should be in the GBs.
I presume this will be what void will ask..Idk, will he want to read through GBs of logging?
This is based on a verbose debug log I have which is 900KB after 4 seconds. Maybe a lot of that is establishing data and it will not take GBs over a few hours. I don't know.

3. Don't know. I don't know why I've seen less freezing when adding new folders besides that some versions ago maybe there was a change that helped against it.

[Herkules97]

Oh yeah, what you could do is maybe keep track of when you started it..Then when it has finished freezing, presuming it was rebuilding..
Check build duration. If say you started rebuilding 00:00 and it finishes 04:00 and it took 2 hours, then it rebuilt twice presumably because in the first time it was outdated by the time it was done.

I forgot to add, build duration is in Tools - Debug - Statistics. Under the Build line. (It takes maybe 3min to open the stats page on the large instance, I haven't counted. It's frozen during that time, to be nice to the process don't click on it..Not that I know if that ultimately worsens anything.)

Total duration: 1:06:50:10

The line I reference.

[void]

Could you please send a mini crash dump when Everything hangs:

• Wait for the Everything UI to hang.
• Download Process Explorer from Microsoft:
  https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
• In Process Explorer, select Everything64.exe (If there is two, select the one using the most memory)
• Right click Everything.exe and under Create Dump, select Create Mini Dump.
• Choose a filename and click Save.
• Please upload this file in a bug report

The mini crash dump will show the reason for the hang.

[Xavierarmand]

Following. I've have\ had similar hangs. I feel like are coming from my nas. At work. Will post more details from home later.