Everything 1.5a Crashing after a few hours on all computers.

[gggirlgeek]

*Everything 1.5.0.1327a x64
*Win10 Pro x64 (on 3 machines.)
*Everything started with Task Scheduler, running with Service, non-admin, using the -instance option.
*Also running Everything 1.4 latest, sharing the v1.5a service. It scans remote folders over Local LAN. Never crashes.
*All of my Everything instances use unique icons, from their own folder.
*All run in portable mode from P:\ drive.

Hello,

My thoughts: A quick glance at the crash log shows some drives not being able to be accessed, even though I don't have those drives enabled in v1.5a options. I'm actually wondering if the problem is with v1.4 because it's sharing the service with v1.5a????? (Although I think it was crashing before the new shared-service option was added recently.)

FYI: I sent a debug log to your email. Everything 1.5 keeps crashing after a few hours of running in the system tray, on 3 different computers in the house. All computers are running, basically, the same Windows 10 Settings and same OS, same Everything.ini settings. The only thing different is the .db database in each. (The main instance is called "1.5a.)

The crashing has been happening for the last 3 or 4 Alpha versions I'd say (the last 6 months.) It seems to just quietly disappear from my system tray. I get no error messages. It doesn't crash while I'm interacting with it. It happens most often on my laptop after waking from sleep, or just being idle for a long time (6 hours or more.) On the 2 desktops, it seems like I've eliminated most of the crashes by correcting my Task Scheduler settings and turning of any options to stop the task on idle or on battery-mode. (I was having trouble with many startup items quitting on me or not starting at all so I'm using Task Scheduler to manage them instead of the default methods. The other startup items are not stopping anymore. 1.5a crashes less often but still does occasionally.)

Everything 1.4 does not crash, ever. Instance, "Everything-Remote," runs at the same time and only makes a folder list of remote LAN drives from the other computers every couple of hours. It does not index or show any local drives. Another instance of v1.4, "No-Exclusions," indexes and access all drives without filters. I run it regularly on all machines and it never crashes either.

I also run another instance of v1.5a, called "Everything-Video," on one desktop and it crashes too, the same way instance "1.5a" crashes. It indexes two drives and filters for video file types.

That's all the info I can think of to share. Thank you so much for this AWESOME program. I love the new Alpha version even more.

[raccoon]

What does the titlebar of your Everything 1.5 say when launched with Task Scheduler?

Does it display the "[Administrator]" flag in the titlebar?

[gggirlgeek]

[Search phrase] - Everything (1.5a) 1.5.0.1327a (x64)
No "Administrator".

[gggirlgeek]

I have a sneaking suspicion resetting my .ini file will help, but... I don't wanna! I have a lot of exclusions, and my colour settings are arranged just how I like. Basically a lot of work went into my settings. Even converting the exclusions to be compatible with v1.5a took some time... I admit, I've recycled my .ini file a lot.

[raccoon]

You don't have to delete anything, just keep a backup copy of your inis and other settings. If you think a single default instance clean install will reveal whether the crashes are coming from a user setting, startup config, instance or task scheduler setting... then it's worth while going down that route until you can faithfully reproduce the crash.

[gggirlgeek]

Yeah, yeah. I know. I guess I'll try it. But it will take a day or two to test it, and my searches will be a pain in the mean time. Also, I think I have to try it with both versions' settings reset or I won't know which one has the problem. Afterwards I have to do the test for a day or two with each. It's going to take a week probably.

First I guess I'll try running a new instance of 1.5a with default settings along with the others and see what happens. Also, I'll stick with v1.5.0.1327a to eliminate another variable.

[raccoon]

Sometimes, just purging the DB and rebuilding the index will fix errant crashes.

[void]

Thank you for the bug report gggirlgeek,

I am sorry to hear Everything is crashing.

FYI: I sent a debug log to your email.

Sorry, I did not receive your email.
Where did you send this email?
Could you please send your Everything.ini to support@voidtools.com



What Search options do you have enabled under the Search menu?
Anything shown on the right side of the status bar?



Could you please put Everything in debug logging mode:

• In Everything, from the Tools menu, under the Debug submenu, check Start Debug Logging.

When Everything crashes, could you please send me your %TEMP%\Everything Debug Log.txt
(please let me know here if you send it, in case it is not received)



Do you have any Everything .dmp files on any of your PCs?



You should have two Everything Services running.
One for Everything 1.4 and one for Everything 1.5.
They are not compatible with each other.

The Everything 1.4 service should be called: Everything
The Everything 1.5 alpha service should be called: Everything (1.5a)

[raccoon]

You should have two Everything Services running.
One for Everything 1.4 and one for Everything 1.5.
They are not compatible with each other.

The Everything 1.4 service should be called: Everything
The Everything 1.5 alpha service should be called: Everything (1.5a)

^ clarity: they are ''compatible'' with each other in that they will run side-by-side without problem nor issue.
they should not interfere with one another or cause the other to crash.

[gggirlgeek]

Hello,

Sorry I took so long. I have been using and logging ES, as well as eliminating a lot of different possible causes for my crashing-problem. Alas! I am still no closer to pinpointing the problem.

When using v1.5a in default-mode (new folder; new .ini; very few options set) it does not crash, but I've tried enabling all options I can think of and haven't been able to crash it.

In my log for the crashing v1.5a there are some messages about a FontCash not being found??? I went into the ES options and set all fonts to default. I also deleted any reference to them in the .ini file. Crashes still abound!

I also cleared any old reference to drives, volumes or folders in the .ini file, basically just leaving the options and the colors and the exclusions set. For extra measure I disabled all FTP or networked settings, and disabled most indexing except for modified and create-dates No success.

So, I've anonymously uploaded my latest logs (just after a crash) for you here. I've included the .ini file, and the crash dump .dmp file, as well as logs for my other non-crashing instances. The archive is password protected and encrypted. I will email the password to you. The link is valid for 15 days.

THANK YOU VERY MUCH!

[void]

Thank you for the Everything.ini and logs gggirlgeek,

I can see the Everything db is being corrupted by the exclusion list somehow..

I am looking into the issue..

[gggirlgeek]

Thank you for looking into it. I do love my Exclusion list. It travels with me on all Windows computers I use, along with my portable programs, on my USB. It has been curated, over many years, to eliminate crud in the OS. While you're looking through my logs I will try a couple of things in my list to see what happens. Unfortunately, I can't make ES crash so I'll have to wait and see after the changes.

Here is a new 7z file with the .dmp files included. I forgot them in the last upload. Sorry. Everything else is the same. I just updated the same archive.

[gggirlgeek]

My first thought is permissions?

Permissions could be a problem for several reasons. (I'll assume it's not restrictions on Recycle.bin or System Volume Information.)

First, all of my Win10 installations, on 4 computers, are generally recycled image backups, restored to new hardware using my backup software (AOMEI Backupper.) So I do run into security issues and registry entries for obsolete User ID's sometimes. I have restored all of my folder permissions back to default but sometimes Windows is stubborn. It's also interesting that crashes are happening on multiple computers that I have set up with all the same settings. I also recycle my ES installations by copying the entire portable partition. So it's very likely user error, I'd say. I have a fresh Win11 install I could test on if needed I suppose.

Second, I wonder about the WinSxS folder exclusion and its hard links. I occasionally edit the filter to "DISABLED WinSxS" when I can't find something. (In v1.4, excluding this folder prevented ES from showing some reparse points in the system. I think this is fixed in 1.5a(??) so I just keep that folder excluded now.) However, it's not excluded in my new, non-crashing ES instance.

[gggirlgeek]

Oh! Forgot to tell you I've updated all 1.5 instances to v1.5.0.1335a.

[NotNull]

@gggirlgeek:

Everything has a new feature to omit files/folders instead of excluding them.
That means they are still in the database, but "parked aside"/ignored and not visible in the results.
For that special occasion where you need to search all files, on the fly you can uncheck 'Enable result omissions', do your thing and check it again. No rebuilding the indexes needed.

Previously, I used a filter (NoNonsense) to keep noise out of the results, but omitting results is more flexible and makes Everything faster (intuitively; didn't measure).
Converting this filter to result omissions wasn't straightforward in all cases, but worth it.


Still curious what causes the current behaviour of your Everything, though ...



Omit Results

[gggirlgeek]

Yeah! I just found this feature yesterday while looking through the forum. I'm excited. I haven't decided, though, when it's best to use Exclusions, Result Omissions, or Filters.

For example, I played with a query I call "No_Crud:" and decided it was best to add it as a filter and make it the default search because I'd like to quickly disable it occasionally.

Filter:

Code: Select all

!"Copy of" !"- Copy" !-disabled !.bak !_bak !.old !_old !_back !.back !ehthumbs.db !thumbs.db !desktop.ini !P:\*\*.ico !P:\*\*.png !P:\*\*.jpg !P:\*\*.bmp

I wonder if moving most of my Exclusions over to Omissions wouldn't solve my crashes. I guess I'll have to test once I track down the offender.

BTW, I haven't had a crash yet today even though I expected a couple. So I may have found something. I'll keep testing and update you.