I'm running Everything 1.3.0.632b; however, the problem has existed for a year or more. I was just hoping it might incidentally have been fixed with the new versions. This is on a WinXP 32-bit system with Intel CPU and 4GB RAM; all service packs.
The symptom is that after a few hours of having Everything running, Windows Explorer becomes unstable. The first symptom is that file associations are lost. The Explorer can't open new windows etc. If I don't reboot Windows around then it will eventually lock up totally.
This only happens if I have Everything running. I suspect a memory leak or other gradually-growing problem. I have checked other posts here and find nothing directly applicable though I did see the advice about looking for symptoms in Task Manager. My case also does involve big drives (4 - 8 TB) and 500-700K files.
Everything is so great and so essential to this use that I can live with the issue, but it would be nice to have it fixed. So I thought I'd mention that there is something wrong.
Thanks,
Arbie
Eventual instability under Win XP
Re: Eventual instability under Win XP
No problems here...I'm using the program from 2 or 3 years and it's working non stop while the pc is on.
Maybe the problem it's because you have so many files.
I have 81276 files and 8316 folders
Maybe the problem it's because you have so many files.
I have 81276 files and 8316 folders
Re: Eventual instability under Win XP
XP, < 1 TB (between two HDDs), 700K files & no issues.
Typically always have Everything open.
Typically do not use Windows Explorer, though if I have, I've never noted any issues.
Only guessing ...
Options | General - Show shell context menus, disable?
Are you opening Windows Explorer from within Everything, outside of it, or you have the same issue regardless?
Or maybe you're running into a shell context menu conflict?
Try ShellExView & note the part, "Right-click is slow or weird behavior caused by context menu handlers".
Typically always have Everything open.
Typically do not use Windows Explorer, though if I have, I've never noted any issues.
Only guessing ...
Options | General - Show shell context menus, disable?
Are you opening Windows Explorer from within Everything, outside of it, or you have the same issue regardless?
Or maybe you're running into a shell context menu conflict?
Try ShellExView & note the part, "Right-click is slow or weird behavior caused by context menu handlers".
Re: Eventual instability under Win XP
Are there any errors reported in your Errorlog.txt file?
How much memory and Handles is Everything using on start-up?
How much memory and Handles is Everything using after a couple hours of usage?
How much memory and Handles is Everything using on start-up?
How much memory and Handles is Everything using after a couple hours of usage?
Re: Eventual instability under Win XP
Thanks for your attention. The problem is not related to the shell interface since I never use that.
In my post dated today (3 Mar 2013) about Everything crashing on folder rename, I attached a screenshot of the file handles etc on startup. I had (but lost) a similar picture after several hours of use... however; I looked at it and there wasn't much difference. Nothing was going crazy.
Below is an excerpt from the Errorlog during a period when this was happening:
I don't have the same instability problem on another Win XP 32-bit machine with only 2GB of RAM, though that is with "only" 4TB being indexed and ~300K files. So I suspect it has to do with the huge amount of data that Everything is dealing with here where it does happen.
--------------
Everything Errorlog
2/23/2013 12:30 PM: Everything 1.3.0.632b: .\src\os.c(5816): os_get_usn_journal(): DeviceIoControl(00000218,FSCTL_QUERY_USN_JOURNAL,0,0,013b0000,56,00e9ef24,0): 1: Failed to query USN Journal.
2/24/2013 7:47 AM: Everything 1.3.0.632b: .\src\os.c(3226): os_open_volume(): CreateFileW(): GetLastError(): 2: Failed to open volume \\?\Volume{632662b3-7e17-11e2-88e0-001fc6733469}
2/24/2013 7:47 AM: Everything 1.3.0.632b: .\src\os.c(3226): os_open_volume(): CreateFileW(): GetLastError(): 2: Failed to open volume \\?\Volume{632662b3-7e17-11e2-88e0-001fc6733469}
2/27/2013 2:07 PM: Everything 1.3.1.636b: .\src\os.c(5729): os_get_usn_journal(): DeviceIoControl(0000021c,FSCTL_QUERY_USN_JOURNAL,0,0,015af068,56,015aef0c,0): 1: Failed to query USN Journal.
2/28/2013 1:03 PM: Everything 1.3.1.636b: .\src\os.c(5729): os_get_usn_journal(): DeviceIoControl(00000224,FSCTL_QUERY_USN_JOURNAL,0,0,015af068,56,015aef0c,0): 1: Failed to query USN Journal.
2/28/2013 1:03 PM: Everything 1.3.1.636b: .\src\os.c(5729): os_get_usn_journal(): DeviceIoControl(00000208,FSCTL_QUERY_USN_JOURNAL,0,0,015af068,56,015aef0c,0): 1: Failed to query USN Journal.
3/2/2013 4:57 AM: Everything 1.3.1.636b: .\src\os.c(5729): os_get_usn_journal(): DeviceIoControl(0000021c,FSCTL_QUERY_USN_JOURNAL,0,0,015af068,56,015aef0c,0): 1: Failed to query USN Journal.
In my post dated today (3 Mar 2013) about Everything crashing on folder rename, I attached a screenshot of the file handles etc on startup. I had (but lost) a similar picture after several hours of use... however; I looked at it and there wasn't much difference. Nothing was going crazy.
Below is an excerpt from the Errorlog during a period when this was happening:
I don't have the same instability problem on another Win XP 32-bit machine with only 2GB of RAM, though that is with "only" 4TB being indexed and ~300K files. So I suspect it has to do with the huge amount of data that Everything is dealing with here where it does happen.
--------------
Everything Errorlog
2/23/2013 12:30 PM: Everything 1.3.0.632b: .\src\os.c(5816): os_get_usn_journal(): DeviceIoControl(00000218,FSCTL_QUERY_USN_JOURNAL,0,0,013b0000,56,00e9ef24,0): 1: Failed to query USN Journal.
2/24/2013 7:47 AM: Everything 1.3.0.632b: .\src\os.c(3226): os_open_volume(): CreateFileW(): GetLastError(): 2: Failed to open volume \\?\Volume{632662b3-7e17-11e2-88e0-001fc6733469}
2/24/2013 7:47 AM: Everything 1.3.0.632b: .\src\os.c(3226): os_open_volume(): CreateFileW(): GetLastError(): 2: Failed to open volume \\?\Volume{632662b3-7e17-11e2-88e0-001fc6733469}
2/27/2013 2:07 PM: Everything 1.3.1.636b: .\src\os.c(5729): os_get_usn_journal(): DeviceIoControl(0000021c,FSCTL_QUERY_USN_JOURNAL,0,0,015af068,56,015aef0c,0): 1: Failed to query USN Journal.
2/28/2013 1:03 PM: Everything 1.3.1.636b: .\src\os.c(5729): os_get_usn_journal(): DeviceIoControl(00000224,FSCTL_QUERY_USN_JOURNAL,0,0,015af068,56,015aef0c,0): 1: Failed to query USN Journal.
2/28/2013 1:03 PM: Everything 1.3.1.636b: .\src\os.c(5729): os_get_usn_journal(): DeviceIoControl(00000208,FSCTL_QUERY_USN_JOURNAL,0,0,015af068,56,015aef0c,0): 1: Failed to query USN Journal.
3/2/2013 4:57 AM: Everything 1.3.1.636b: .\src\os.c(5729): os_get_usn_journal(): DeviceIoControl(0000021c,FSCTL_QUERY_USN_JOURNAL,0,0,015af068,56,015aef0c,0): 1: Failed to query USN Journal.
Re: Eventual instability under Win XP - FIXED
FYI, it looks like v1.3.1.636b has fixed this instability issue. THANK YOU!
Now, I eagerly await the next release with the fix for crashes when folders are renamed...
http://forum.voidtools.com/viewtopic.php?f=6&t=1716
Searching in order to rename things is the only reason I have to drop back to the old version.
Now, I eagerly await the next release with the fix for crashes when folders are renamed...
http://forum.voidtools.com/viewtopic.php?f=6&t=1716
Searching in order to rename things is the only reason I have to drop back to the old version.