Everything stops searching when searching file content at some point.

[pickwick]

I need to search many files in some directory tree for some keywords and those files are of a lot of different types and sizes. At first I'm trying to define filters to only search for the files I'm mostly interested in, but at some point Everything simply needs to search all of those for the keywords I need.

Searching WITHOUT looking at contents seem to work properly, but whenever I add a content filter, Everything starts to search, I see CPU- and I/O-load, but simply stops after a few seconds. I've already waited a few minutes, but Everything doesn't seem to do anything afterwards anymore, there won't be any additional load in the process. While some options of the GUI still seem to work, the control showing results doesn't seem to respond properly anymore. When trying to change columns, the GUI starts to look glitchy and the rendering isn't updated anymore. Sometimes I'm somehow even able to trigger an additional dialog if I want to abort the current search. Though, doing so doesn't rescue the GUI anymore, the process needs to be shut down forcefully.

Code: Select all

!.svn !branches !tags size:<=10mb C:\Users\tschoening\Documents\Svn\Bin\ content:"AM-SoFT GmbH IT-Systeme" 

I've already enabled verbose debugging, but don't see any additional useful pieces of information. The log file contains the following only:

Code: Select all

2021-01-15 11:00:05.769: Everything
2021-01-15 11:00:05.780: Version 1.4.1.1003 (x64)
2021-01-15 11:00:05.785: Windows NT 6.2
2021-01-15 11:00:05.790: Processors 8
2021-01-15 11:00:05.795: IsAdmin 0
2021-01-15 11:00:05.806: AppData 1
2021-01-15 11:00:05.811: Service 0
2021-01-15 11:00:05.815: cmdline "C:\Program Files\Everything\Everything.exe" 
2021-01-15 11:00:05.820: load localization
2021-01-15 11:00:05.826: lng file opened!
2021-01-15 11:00:05.830: header size 946
2021-01-15 11:00:05.836: version 1
2021-01-15 11:00:05.841: got header
2021-01-15 11:00:05.845: system default lid 0407
2021-01-15 11:00:05.848: count 39
2021-01-15 11:00:05.854: ole initialize: 00000000
2021-01-15 11:00:05.857: create mutex
2021-01-15 11:00:05.860: mutex exists
2021-01-15 11:00:05.862: send cl
2021-01-15 11:00:05.865: send message ok
2021-01-15 11:00:05.867: mutex exists
2021-01-15 11:00:05.870: shutdown
2021-01-15 11:00:05.872: kill
2021-01-15 11:00:05.876: event start 0000000000000000

Additionally, looking at the process using Process Explorer reveals the following stacktrace:

Code: Select all

ntoskrnl.exe!KeSynchronizeExecution+0x5b66
ntoskrnl.exe!KeWaitForMutexObject+0x1460
ntoskrnl.exe!KeWaitForMutexObject+0x98f
ntoskrnl.exe!KeWaitForMutexObject+0x233
ntoskrnl.exe!ExWaitForRundownProtectionRelease+0x7dd
ntoskrnl.exe!KeWaitForMutexObject+0x3a29
ntoskrnl.exe!KeWaitForMutexObject+0x1787
ntoskrnl.exe!KeWaitForMutexObject+0x98f
ntoskrnl.exe!KeWaitForMutexObject+0x233
ntoskrnl.exe!KeWaitForMultipleObjects+0x45b
win32kfull.sys!xxxUpdateInputHangInfo+0x10d7
0x0000000000000000
win32u.dll!NtUserWaitMessage+0x14
Everything.exe+0xcf2d5
Everything.exe+0x1a9c91
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

I've already re-installed and used Everything with various different options as well: With service and without, with admin-permissions and without, with additional manual folder indexing and without etc.

The only workaround so far seems to be to reduce the number of files to search in by searching more specific child directories one after another. But that makes the whole process pretty difficult, because one can't know beforehand if some directory works at all or not and only very few files contain the keywords I'm actually looking for. Would be great to NOT need to maintain a list of child dirs searched for already or alike.

Any idea on what the problem might be? Thanks!

[void]

Thank you for your post and logs.

Everything might be getting stuck reading the file content from a certain iFilter.

Please try enabling verbose debug logging when Everything is already running:

• In Everything, type in the following search and press ENTER:
  /verbose
• Type in the following search and press ENTER:
  /debuglog
  This will enable verbose debug logging. The log is written to %TEMP%\Everything Debug Log.txt
• Please try your content search, eg:
  !.svn !branches !tags size:<=10mb C:\Users\tschoening\Documents\Svn\Bin\ content:"AM-SoFT GmbH IT-Systeme"

When Everything appears to hang, what is shown at the end of the debug log?

You should see something like:

content <filename>
iFilter 0x0123456701234567
get chunk FAILED/OK/done
get text FAILED/OK/done
failed to init ifilter
failed to load stream
failed to get IID_IPersistStream from stream
create stream from <filename> failed
No iFilter for <filename>
IPersistStream::QueryInterface exception 0x00001234
IPersistStream::Load exception 0x00001234
IFilter::Init exception 0x00001234
IFilter::GetText exception 0x00001234
IPersistStream::Release exception 0x00001234
IStream::Release exception 0x00001234
IFilter::Release exception 0x00001234

Please restart Everything to stop debug logging as the logs can grow very large:

• In Everything, type in the following search and press ENTER:
  /restart
  -If Everything has hung, please terminate Everything with the Task Manager (Ctrl + Shift + ESC)

[pickwick]

When running into this problem with Everything I've tried an alternative search tool named TreeSize I already own as well. I get a somewhat similar problem in that tool as well, but because it's a different one, doesn't use an index etc., it didn't think things were related. So I described the problem in TreeSize to their support and they answered me that this problem is known to them when using the default PDF iFilter provided with Windows. As I didn't install any other one knowingly, that is most likely the reason for the problems with TreeSize.

Might the same problem happen with Everything as well? Will try the Adobe iFilter when I'm able to restart my system:

https://supportdownloads.adobe.com/deta ... ftpID=5542

[NotNull]

... or https://www.pdflib.com/download/tet-pdf-ifilter/
- or -
https://www.sumatrapdfreader.org/downlo ... iewer.html


Some time ago I had a similar issue (Everything kept waiting) caused by what I thought to be a corrupt PDF, but that could just as well be caused by the problem you linked to.

FWIW: I deleted the corrupt PDF, installed SumatraPDF (including iFilter) and never had any related issues after that.

[pickwick]

It seems that installing the Adobe iFilter makes my search succeed instantly again. I wonder if a filter removing PDF files would have succeeded as well? Though, I need to search PDFs, so will stay with what I have now. Thanks for your help!