Crashes consistently after entering 'ki'

[terrypin]

I was actually searching for 'kicad', but if I paused (initially for whatever reason, later deliberately), the program crashed unceremoniously. Opening it again from its taskbar icon restored all 5.3 M indexed files immediately. I've closed Everything altogether for now but will re-open later and, if it might help, take a quick screenshot befor 'ki' crashes. Meanwhile, any thoughts on likely cause?

[terrypin]

Still pursuing this but looks to be due to a couple of obscure files with Date Modified entries of 01/01/80.

That's a couple of years before I recall first using the newly introduced 'PC'. And decades before that file could have appeared on my current system! So clearly aberration or accident of some sort.

As you see, the file itself is in one of two folders whose existence/purpose is a mystery to me.





I'm in the process of deleting the assumed culprits and their daily and weekly backups.

Any insights please?

[therube]

While 1-1-1980 is the beginning of "DOS" time, what I find more interesting is the time itself, which is "00:00".

Everything doesn't have any issues with dates of 1-1-1980, nor dates before that.
But maybe the 00:00 is throwing it?
(And I'm not sure how to create a file with that time?)


Why do my file creation, access, or modified time disappear if I set it to midnight on January 1, 1980?
How to recognize different types of sentinel timestamps from quite a long way away
.

Code: Select all

C:\out\>nircmd.exe setfiletime XXX "1-1-1980 0:0:0" "1-1-1980 0:0:0"
C:\out\>DIR XXX

Directory of C:\out

05/10/1618  01:54 AM            19,248 XXX

Code: Select all

C:\out\>touch -t 198001010000 XXX
C:\out\>DIR XXX

Directory of C:\out

01/01/1980  12:00 AM            19,248 XXX

[terrypin]

Thanks, interesting, never come across a 'sentinel timestamp' before. Prompts recall of a favourite movie.
https://www.dropbox.com/scl/fi/757jy7bw ... aoij&raw=1

[NotNull]

Could you try the following search to find out if Everything trips over these KI files?

Code: Select all

!exact:ki   ki

If Everything does not crash with this search, there is something with these files that Everything does not like. Most likely some Windows shell extension.
Could you attach them (or upload them elsewhere) for further inspection?

[terrypin]

Your search string crashes as before.
I used PrttScn again and show results below.
I had previously moved the original to external drive J: But despite being renamed to 'bad-ki-bad' it still crashed. I think it must be the cause of the crash. Hang on, I'll rename it again as 'badxyz'...

No, to my surprise Everything found 'badxyz' as the only hit but did not crash.

Nor does you '!exact:ki ki' search crash, of course.

Note that Everything still shows 01/01/80 as Date Modified. (No other hits have that.) Incidentally,t File Explorer has Date Modified blank for badxyz.

I'm perplexed, as I'd assumed that it was a file/time stamp issue. But doesn't this latest test disprove that? If I open J:\badxyz in Hxd Editor it looks exactly the same as I showed before.

I'll try to send you J:\badxyz. Seems pointless sending copies of all the rest?
https://www.dropbox.com/scl/fi/oodkcatg ... 576n&raw=1

[therube]

the file itself is in one of two folders whose existence/purpose is a mystery to me

Looks to relate to Kiribati. And more specifically, islands of Kiribati.
And given that the file looks to deal with (google Chrome) "AutofillStates" (which I guess is supposed to be kind of like AI), I'd say the file itself (& most likely its' odd date too, are just a red herring), I'm thinking it is (as mentioned) a shell extension. (Which was actually my first thought, before seeing the date.)

And the fact that:

I'll rename it again as 'badxyz'...
No, to my surprise Everything found 'badxyz' as the only hit but did not crash.

did not crash, is because the actual trigger of the crash, which is not the particular file in question, did not bring up other hits (results) which is where the actual issue lies. Your original search did contain various picture file types along with .asy & .lib (HxD) files, all of which are associated with various programs & it is likely one of them that is causing the issue (I'm guessing).

If you took your same list of files, (copied them) & renamed them all to badxyz(#).(orig ext), & then searched on 'badxyz' (such that all the same files would be found, only named differently, that you would again crash.

So try, disable context menu shell extensions in Everything & see if 'ki' no longer crashes (after having renamed, or copied, badxyz back to ki).


PS: You can set up Everything to directly open any file with HxD, & assign a hotkey to that action.
custom_open_command04=$exec("C:\BIN\HEX.exe" %*)
(Oh, & I've renamed HxD.exe to HEX.exe.)