Everything crash

[nothing]

First of all, many thanks for your product!

It seems to be one of the best tools I've ever seen and judging from your replies/support here you're continually developing and improving it considering users feedback.

Big up!

I've installed the latest beta version of Everything v1.3.2.649b. I'm running it standalone without service enabled (it just sits in the tray). Everything starts on Windows 7 x64 SP1 under admin privileges with UAC turned off.

Set up few NTFS local volumes + 2 network mapped drives with exclusion lists (some of the exclusions are paths on the network mapped drives to prevent duplicates).

1. Everything crashes randomly at night on update for some reason - how do I enable log to check?

here is a log from eventwvr.msc:

Code: Select all

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2013-05-14T23:23:15.000000000Z" /> 
  <EventRecordID>12877</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>COMPUTER</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>Everything.exe</Data> 
  <Data>1.3.2.649</Data> 
  <Data>5188ba33</Data> 
  <Data>Everything.exe</Data> 
  <Data>1.3.2.649</Data> 
  <Data>5188ba33</Data> 
  <Data>c0000005</Data> 
  <Data>00010a4e</Data> 
  <Data>147d4</Data> 
  <Data>01ce50347a04ba31</Data> 
  <Data>C:\Program Files (x86)\Everything\Everything.exe</Data> 
  <Data>C:\Program Files (x86)\Everything\Everything.exe</Data> 
  <Data>3fffdc12-bced-11e2-8895-e90b83995d3e</Data> 
  </EventData>
  </Event>

2. When I add or modify NTFS drives it forces to rebuild whole database (including network shares) - any chance to avoid network shares (in Folders setting) rescanned?

3. When I add or modify exclusions list - it rescans whole thing again instead of just excluding certain folders or files from the existing database.

4. Also I noticed on beta version it seems to be building an index a bit longer for NTFS drives than on 1.2 stable version. I guess its normal or not?

5. Everything main window and settings window hangs if you change any settings in the Folders section (attempting to rescan folders specified there). Any chance to make rescanning button maybe somewhere or make it manual? (Simple scenario: if I want to change update hours to 72 hours it forces to index update instead of just changing setting).

6. Another suggestion I have in mind to implement searching whilst there is still update process going on in the background (only on the already indexed drives/folders).

Sorry for my english, I'm not a native speaker.

Thanks again.

[void]

Thanks for the bug report.

1. Everything crashes randomly at night on update for some reason - how do I enable log to check?

I am aware of the issue.
I have found that deleting short named folders will corrupt the database.
This will cause Everything to crash after updating the folder indexes.
I will post a fix soon.

To enable debug logging:
Debugging Help

A crash dump might be more helpful in this situation:
Crash Dump Help

2. When I add or modify NTFS drives it forces to rebuild whole database (including network shares) - any chance to avoid network shares (in Folders setting) rescanned?

The entire database needs to be re-sorted when adding or removing an index.
Everything takes the easy way out and just rebuilds the entire database...
Adding or removing an NTFS volume, folder or filelist from the index without rebuilding the entire index is on my things to do list.

3. When I add or modify exclusions list - it rescans whole thing again instead of just excluding certain folders or files from the existing database.

Same issue as above.

4. Also I noticed on beta version it seems to be building an index a bit longer for NTFS drives than on 1.2 stable version. I guess its normal or not?

I find that indexing on 1.3 is nearly twice as fast as 1.2.
Please run Everything in debug mode.
Everything will report a timing profile of the build in the debug console.
What is displayed in the debug console when you build an index with 1.2 and 1.3?
How many cores does your CPU have?

5. Everything main window and settings window hangs if you change any settings in the Folders section (attempting to rescan folders specified there). Any chance to make rescanning button maybe somewhere or make it manual? (Simple scenario: if I want to change update hours to 72 hours it forces to index update instead of just changing setting).

Currently, Everything should just apply the new scheduled update time without re-indexing.
Did you change any other settings?

6. Another suggestion I have in mind to implement searching whilst there is still update process going on in the background (only on the already indexed drives/folders).

I will consider an option to allow searching while Everything is indexing a folder.

Thanks for the suggestions.

[nothing]

Thanks for the bug report.
I am aware of the issue.
I have found that deleting short named folders will corrupt the database.
This will cause Everything to crash after updating the folder indexes.
I will post a fix soon.

To enable debug logging:
Debugging Help

A crash dump might be more helpful in this situation:
Crash Dump Help

thanks, but:

Code: Select all

Everything.exe -debug > out.txt

doesn't work saying can't open filelist c:\program files (x86)\Everything\out.txt

debug console works tho

I find that indexing on 1.3 is nearly twice as fast as 1.2.
Please run Everything in debug mode.
Everything will report a timing profile of the build in the debug console.
What is displayed in the debug console when you build an index with 1.2 and 1.3?
How many cores does your CPU have?

I have Intel Core 2 Duo T7500 2.2Ghz processor (2 cores).

Currently, Everything should just apply the new scheduled update time without re-indexing.
Did you change any other settings?

No, i didn't, strangely it works now without re-indexing, what I did - changed from 1 day to custom hours update interval.

Many thanks for the quck answer!

[void]

Everything.exe -debug > out.txt

This will only work from a command prompt.
This will fail as you described if you try to run this from a shortcut.

[nothing]

Everything.exe -debug > out.txt

This will only work from a command prompt.
This will fail as you described if you try to run this from a shortcut.

I ran from command line and from the shortcut -- same result.

[nothing]

sent you a link with crashdump file, hope it helps.

unfortunately debug log is not available, because when crash happened console closed too, but Everything didnt save log anywhere ..

[void]

Thanks for the Everything dump.
Unfortunately, the dump does not provide any useful debug information (due to stack and register corruption).

I am aware of the issue with logging the debug output to a file.

What do you currently have set for the Choose when to check for solutions to problems reports option?

You can find this setting here:
Control Panel\System and Security\Action Center\Problem Reporting Settings

Try changing it to:
Each time a problem occurs, ask me before checking for solutions.

[nothing]

Thanks for the Everything dump.
Unfortunately, the dump does not provide any useful debug information (due to stack and register corruption).

I am aware of the issue with logging the debug output to a file.

What do you currently have set for the Choose when to check for solutions to problems reports option?

You can find this setting here:
Control Panel\System and Security\Action Center\Problem Reporting Settings

Try changing it to:
Each time a problem occurs, ask me before checking for solutions.

thanks, just did that.

I'm running everything with debug now from the console (thanks to other guy who posted the question so I figured how to start it properly), will wait until the issue reproduces and send you a crashlog.

Thanks

[nothing]

Any update? I can't seem to spot an error in Everything with debug mode, it writes nothing to the output file for some reason ..

I'm now on stable version, it works stable as rock.

But would love to use new version because of the shared folders indexing functionality.

I think the crash is related to shared folders indexing and exclusions maybe.

[void]

I hope to post an update at the end of the week which should fix the issue.

For now, please try turning off NTFS monitors and Folder updating.

[nothing]

I hope to post an update at the end of the week which should fix the issue.

For now, please try turning off NTFS monitors and Folder updating.

thanks for this, i'll wait for an update, staying on Everything 1.2 stable version for now.

[void]

"Everything" version 1.3.3.653b or later should fix the issue.

[nothing]

after testing for quite some time I'm glad to report v1.3.3.656 is working just fine!

many thanks, void!