Crashing - v 1.5 alpha

[Trevor22]

I recently installed v 1.5 alpha (64 bit) and began indexing content. Each time I launch Everything, it crashes after a few minutes of it. I see a log file being generated. Can I find the reason for the crash in that file?

[void]

Thank you for the crash report.

What version of Everything are you using? (Help -> About)

Please make sure you are using the latest Everything 1.5 Alpha.



Could you please send a mini-crash dump to support@voidtools.com:

• Keep the crash dialog open.
• Download Process Explorer from Microsoft:
  https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
• In Process Explorer, select Everything.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 send this file to support@voidtools.com

Please try a complete database rebuild:

• Exit Everything (right click the Everything tray icon and click Exit).
• Delete your %LOCALAPPDATA%\Everything\Everything.db
• Restart Everything.

Normally Everything does not write any log files.

If you can, before Everything crashes:

• Enable Debug Console.
  -or-
• Enable Debug Logging.

Alternatively, start Everything.exe with the -debug-log command line option.



The crash might be related to an iFilter for content indexing.
Does the crash occur if you disable content indexing under Tools -> Options -> Content?

[Trevor22]

I'm using version 1.5.0.1269a (x64). I ran process explorer and saw that Everything quickly used up 13 gigs of memory, before it crashed when there was no usable memory available.

I tried creating a minidump with process explorer, but I received "access denied error" . I also turned out the console and watched it grind to a halt when the memory reached 100 percent.

[void]

Thank you for the information.

The grind to a halt is caused by Everything being paged to and from disk.

Everything is not designed to index gigabytes of content.
Content is stored in memory.

Please try reducing the number of files Everything content indexes:

• In Everything, from the Tools menu, click Options.
• Click the Content tab on the left.
• Set include only folders to a semicolon delimited list of folders, for example:
  c:\users\<my user name>\Documents
• Click OK.

Alternatively, disable content indexing in Everything and use Windows Indexing which can be accessed with the si: search function.

For example:
si:"my content"

[Trevor22]

I followed these instructions--turned off content indexing and used the "sl" directive. This time, it did not use much memory, but it still crashed after about 1 minute. The console crashed too, and I was unable to save a dump.

[void]

I tried creating a minidump with process explorer, but I received "access denied error" .

Please try running Everything 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.

-or-

Run Process Explorer as an admin.



Please try the verbose debug console:

• In Everything, from the Tools menu, under the Debug submenu, click Console.
• From the Tools menu, under the Debug submenu, click Verbose.
• Wait for Everything to crash
  ---The console will crash too, this is expected. However, it should be possible to take a screenshot of the console.
• What is shown in the debug console? Please send a screenshot to support@voidtools.com

[Trevor22]

screenshot sent

[void]

Thank you for the screenshot.

The Everything database is 'blocking' (freezing) because the previous si: search is taking to long to cancel.

I am working on a fix..


For now, the best approach I can offer is to type out your si search without the colon and add the colon last.

For example:

si"my content search"
and finally add the :
si:"my content search"

[Trevor22]

Thank you.

[Trevor22]

The "si:" function is working great for most files, but it does not locate contents of .pst/.ost files. I've read that the Windows stores the content in these files in a separate index. Not sure if that's correct, but is it possible to use a Window search index to search this content?


(I originally posted this question in the general forum, but deleted it and am posting here instead).

[tuska]

The "si:" function is working great for most files, but it does not locate contents of .pst/.ost files. I've read that the Windows stores the content in these files in a separate index. Not sure if that's correct, but is it possible to use a Window search index to search this content?

(I originally posted this question in the general forum, but deleted it and am posting here instead).

In case you might be interested:
In the forum "General" there is already the topic "Outlook".
The topic is even still quite fresh

[Trevor22]

In case you might be interested:
In the forum "General" there is already the topic "Outlook".
The topic is even still quite fresh

Thanks. I think my issue is a little bit different than the one addressed in that topic, but I just posted there.

[void]

Everything 1.5.0.1270a fixes an issue with Everything blocking (hanging/freezing) when cancelling the previous search takes too long.