Everything crashes on 2nd search

[ccb2019]

Win10 Pro 1809
Everything 1.4.1.9035

I noticed this behavior when Everything was installed with Take Command.
I uninstalled TC, downloaded Everything from the voidtools web site, and installed it.
When I start Everything and type something in the search box, it seems to scan the whole disk, sorts folder names, and returns a list of matches.
If I type something else in the search box, Everything closes - no message, it just closes.

What's going on? Is there a log file somewhere?

I don't think I ever saw this behavior on Win10 1803.

[void]

Thanks for the bug report.

Could be a corrupt database, please try the following:

• Completely exit Everything (right click the Everything system tray icon and click Exit)
• Delete your %LOCALAPPDATA%\Everything\Everything.db
• Restart Everything
• Everything will reindex which may take a few minutes.
• After indexing is complete, does Everything crash after typing in a search?

[ccb2019]

Thanks for the reply.
I followed your instructions, same issue persisted.
Next, I uninstalled Everything, restarted the computer, installed Everything.
Same issue exists:
- Start Everything, type in something to search for.
- When Everything (finally) finishes indexing/sorting, search results are displayed.
- Highlight search term, press Backspace, start typing new search, Everything exits, nothing in Task Manager.

[therube]

when Everything was installed with Take Command

How do you go about intalling Everything with TC?

downloaded Everything from the voidtools web site, and installed it

Any change if you download the ZIP build, unzip it into some temporary directory, & run it?

(finally) finishes

About how long does it take to finish?
About how many files/drives do you have?

[therube]

As a test, in from within a new, temporary directory (say, C:\TEST_EV\), with only everything in it...

If you run (from a C:\ prompt):

C:\TEST_EV\

Code: Select all

    everything.exe  -instance NODB  -choose-volumes

(Running that command, you will not see anything happen except that you are returned to a C: prompt & that an Everything .ini file will be created.)

Followed by:

C:\TEST_EV\

Code: Select all

everything -instance NODB -read-only

Everything should open.
No results will display.

Can you at that point type in multiple search queries (& even though no results will show up) without Everything quitting?

[therube]

If you test with an older version, say 1.3.4, can you run that successfully?
https://www.voidtools.com/support/every ... _versions/

[ccb2019]

when Everything was installed with Take Command

How do you go about intalling Everything with TC?

When I install JPSoft's Take Command, it offers to install Everything. (Has offered for the last several versions.)

downloaded Everything from the voidtools web site, and installed it

Any change if you download the ZIP build, unzip it into some temporary directory, & run it?

Nope, same bad behavior.

(finally) finishes

About how long does it take to finish?

:: Several minutes. 5? 15?

About how many files/drives do you have?

:: 1 nominal 500GB SSD. ~3.8M objects (files and folders) according to UltraSearch.

[ccb2019]

C:\TEST_EV\

Code: Select all

everything -instance NODB -read-only

Everything should open.
No results will display.

Can you at that point type in multiple search queries (& even though no results will show up) without Everything quitting?

Yes, multiple searches can be run w/ no results returned.

[void]

Thanks for the info.

Is both the x86 and x64 version crashing?

Could you please enable verbose debug logging:

• Completely exit Everything (Right click the Everything system tray icon and click Exit)
• Run Everything with verbose debug logging enabled with the -debug-log and -verbose command line options:
  Everything.exe -debug-log -verbose
• After Everything has crashed, what is shown on the last page of your %TEMP%\Everything Debug Log.txt ?

[ccb2019]

Installed fresh copy of the x64 portable version.
Started Everything:
2019-05-14 17:09:03.676: cmdline "C:\bin\Everything-1.4.1.935.x64\Everything.exe" -debug-log -verbose

Not sure what you mean by "last page" of a 538-line text file, so I attached the whole thing.
Nope, can't seem to attach a text file -- "Invalid file extension -- " .
I've tried .txt, .log, no extension. What's going on with that?

Here is a large portion of the file, with ~280 MSGFILTER lines removed.
2019-05-14 17:09:04.434: CreateFileW(): GetLastError(): 5: Failed to open volume \\?\Volume{}
2019-05-14 17:09:04.438: opened -1 0.007113
2019-05-14 17:09:04.442: access denied \\?\Volume{}
2019-05-14 17:09:04.446: is out of date volume available C:: 0
2019-05-14 17:09:04.450: check for file list changes
2019-05-14 17:09:04.454: checked for file list changes in 0.003932 seconds
2019-05-14 17:09:04.457: search '' filter '' sort 0
2019-05-14 17:09:04.460: termtext
2019-05-14 17:09:04.464: term 00000000004c7390, flags: 3140, next: 0000000000000000, notnext: 0000000000000000
folderop: 0, fileop: 0, term:
2019-05-14 17:09:04.467: create thread
2019-05-14 17:09:04.471: EVENT: 00000001400531a0 00000000004cf330
2019-05-14 17:09:04.474: EVENT: 0000000140019ce0 0000000000479790
2019-05-14 17:09:04.477: EVENT: 00000001400531a0 00000000004cf330
2019-05-14 17:09:04.480: EVENT: 000000014005cb30 00000000004cf330
2019-05-14 17:09:04.484: EVENT: 00000001400531a0 00000000004cf330
2019-05-14 17:09:04.487: MSG: 00000000001b0d54 0060 0000000000000001 0000000000000000
2019-05-14 17:09:04.492: SET SORT 0
2019-05-14 17:09:04.495: MSG: 0000000000020c66 0402 0000000000000000 0000000000000000
2019-05-14 17:09:04.498: found 0 folders, size 0, db search time taken: 0.000004 seconds
2019-05-14 17:09:04.502: found 0 files, size 0, db search time taken: 0.000000 seconds
2019-05-14 17:09:04.505: set sort 0 1
2019-05-14 17:09:04.509: already sorted
2019-05-14 17:09:04.512: finished sort, time taken 0.006430 seconds
2019-05-14 17:09:04.515: update selection 0.000000 seconds
2019-05-14 17:09:04.518: MSG: 0000000000020c24 000f 0000000000000000 0000000000000000
2019-05-14 17:09:04.522: MSG: 00000000001b0d54 0738 0000000000000000 0000000000000000
2019-05-14 17:09:04.529: MSG: 0000000000040c46 1401 0000000000000000 0000000000000000
2019-05-14 17:09:04.532: EVENT: 0000000140053150 00000000004cf330
2019-05-14 17:09:04.536: EVENT: 00000001400531a0 00000000004cf330
2019-05-14 17:09:04.539: EVENT: 0000000140019ce0 0000000000479790
2019-05-14 17:09:04.543: DB_WAIT: _db_ready_proc waiting...
2019-05-14 17:09:04.547: DB_WAIT: _db_ready_proc waited 0.003902 seconds
2019-05-14 17:09:04.550: EVENT: 000000014005cb50 00000000004cf330
2019-05-14 17:09:04.553: when ready 8 0000000000000000 0000000000000000
2019-05-14 17:09:04.556: EVENT: 0000000140053150 00000000004cf330
2019-05-14 17:09:04.560: new results 0
2019-05-14 17:09:04.563: MSG: 0000000000040c46 1401 0000000000000000 0000000000000000
2019-05-14 17:09:04.567: MSG: 0000000000020c66 0402 0000000000000000 0000000000000000
2019-05-14 17:09:04.571: MSG: 0000000000020c24 000f 0000000000000000 0000000000000000
2019-05-14 17:09:04.577: MSG: 0000000000000000 0113 0000000000001708 00007ffad0aa7e50
2019-05-14 17:09:04.581: MSG: 0000000000470a36 0113 0000000000000001 0000000000000000
2019-05-14 17:09:04.585: MSG: 0000000000020c24 0113 000000000000002d 0000000000000000
2019-05-14 17:09:04.588: MSG: 0000000000000000 0113 0000000000001706 00007ffad0aa7e50
2019-05-14 17:09:04.592: MSG: 00000000000b0be8 0118 000000000000ffff 0000000000000118
2019-05-14 17:09:04.604: WM_ACTIVATE 0000000000000000 00000000000a0b4a, lastfocus 00000000000b0be8, current focus 00000000000b0be8
2019-05-14 17:09:04.615: MSGFILTER: 00000000000a0b4a 031f 0000000000000001 0000000000000000
/* snip ~280 MSGFILTER lines */
2019-05-14 17:09:11.959: MSGFILTER: 00000000001f033c 0113 00000000025b8db0 00007ffacd363950
2019-05-14 17:09:11.985: MSGFILTER: 00000000001f033c 0202 0000000000000000 0000000000160028
2019-05-14 17:09:11.996: Enter ShellExecute
2019-05-14 17:09:14.456: Leave ShellExecute
2019-05-14 17:09:14.516: WM_ACTIVATE 0000000000000001 00000000000a0b4a, lastfocus 00000000000b0be8, current focus 00000000000a0b4a
2019-05-14 17:09:14.526: MSG: 0000000000000000 0012 0000000000000000 0000000000000000
2019-05-14 17:09:14.530: shutdown
2019-05-14 17:09:14.533: destroy ui
2019-05-14 17:09:14.547: WM_ACTIVATE 0000000000000000 0000000000000000, lastfocus 00000000000b0be8, current focus 00000000000b0be8
2019-05-14 17:09:14.590: processed usn records in 0.000001 seconds
2019-05-14 17:09:14.593: db_save_local 0 folders, 0 files
2019-05-14 17:09:14.605: saved db: 0.015730 seconds
2019-05-14 17:09:14.608: read_directory_changes stop thread
2019-05-14 17:09:14.612: read_directory_changes stop get fd thread
2019-05-14 17:09:14.615: read_directory_changes remove events
2019-05-14 17:09:14.618: read_directory_changes free events
2019-05-14 17:09:14.622: read_directory_changes remove got fd events
2019-05-14 17:09:14.626: read_directory_changes free got fd events
2019-05-14 17:09:14.628: read_directory_changes after update events
2019-05-14 17:09:14.632: read_directory_changes free monitors
2019-05-14 17:09:14.653: Enter ShellExecute
2019-05-14 17:09:16.721: Leave ShellExecute
2019-05-14 17:09:16.735: kill
2019-05-14 17:09:16.740: event start 0000000000000000


Thanks for looking in to this.

[void]

Thanks for the debug logs.

Did Everything crash when you had Everything running with -debug-log -verbose?

It looks like Everything shutdown gracefully.

Not sure what you mean by "last page" of a 538-line text file

Just the last few lines is fine, thanks.

[ccb2019]

"It looks like Everything shutdown gracefully."
What the ... ??
- I enter a filename to search for.
- I select the entire search word and clear it with the Backspace key.
- Everything crashes.

Is that the expected functionality/workflow?
- Start Everything, wait while it uses ~90% of CPU for several minutes
- Conduct one (1) search; Everything crashes.
- Start Everything, wait while it scans and indexes entire 500GB SSD again....

Where is the 'grace' in any of that?

[ccb2019]

"Did Everything crash when you had Everything running with -debug-log -verbose?"
Yes.

[NotNull]

"It looks like Everything shutdown gracefully."
What the ... ??
- I enter a filename to search for.
- I select the entire search word and clear it with the Backspace key.
- Everything crashes.

Is that the expected functionality/workflow?
- Start Everything, wait while it uses ~90% of CPU for several minutes
- Conduct one (1) search; Everything crashes.
- Start Everything, wait while it scans and indexes entire 500GB SSD again....

Where is the 'grace' in any of that?

Everything doesn't crash! It closes itself on an (for now) unexpected moment, but that is not the same (from a technical perspective).
In the logfile you posted there is an entry

2019-05-14 17:09:14.530: shutdown

, meaning Everything runs it's normal closing routine and is able to finish that routine ("shutdown gracefully.").

But you are right,that's not what normally happens when entering a new search (otherwise this forum would be flooded with frustrated people like you).


I can't really help you to analyze the debug log (so be nice to @void ), but one thing stood out:

Code: Select all

2019-05-14 17:09:04.434: CreateFileW(): GetLastError(): 5: Failed to open volume \\?\Volume{}
2019-05-14 17:09:04.438: opened -1 0.007113
2019-05-14 17:09:04.442: access denied \\?\Volume{}

Maybe there is an issue with one of your disks?

• Right-click the disk in Explorer
• Choose Properties from the context menu
• Go to the Tools tab
• Run Error checking

BTW: If Everything - or any other application - crashes, it would generate an entry in the Eventlog

[void]

There's nothing graceful about it, it's just the log appears to show Everything exiting normally without crashing (as if you exited Everything normal)

I think you are running Everything as a standard user with the run as administrator option enabled.

When you run Everything with this option enabled, it will check if Everything is running as administrator and if it is not running as administrator, Everything will relaunch as administrator. We are seeing the debug log from that first process which will immediately exit.

Could you please try running Everything with debug logging again, but this time from an admin command prompt:

• From an admin command prompt, navigate to your Everything.exe location, eg:
  cd "c:\program files\Everything"
• Launch Everything with debug logging enabled:
  Everything.exe -debug-log -verbose

[void]

Everything closes - no message, it just closes.

I'm getting quite a few reports of this happening recently.

Common theme seems to be a windows update in 1809.

If anyone is having trouble with Everything just disappearing after typing in a search, could you please:

• Completely exit Everything (right click the Everything system tray icon and click Exit)
• From the Start menu, click Run
• Type in the following and press ENTER:
  cmd
• In the command prompt, navigate to your Everything installation folder:
  cd "c:\program files\Everything"
• Launch Everything in debug mode and redirect output to out.txt
  Everything.exe -debug > %temp%\out.txt
• After typing in a search in Everything, and after Everything has disappeared, could you please send your %TEMP%\out.txt to support@voidtools.com

It could be related to an icon rendering issue, please try Everything 1.4.1.942:
https://www.voidtools.com/forum/viewtopic.php?f=5&t=7535

[void]

Please try Everything 1.4.1.948 for a fix.