On Thu, 18 Apr 2019 16:12:03 -0400, Paul wrote:

Olie wrote:

Working on my Win XP Pro laptop and see that the CPU available is 0%

Process Explorer shows:
two copies of Everything eating up 60%
why two copies ?
one copy of Seamonkey eating all the rest.

Killed all Everything and Seamonkey ate even more.

Why can't these programmers write proper code ?

I had to Kill all those apps to get to use my laptop.

Probably no easy fix on my end but I'll ask anyway.

Any fix ? Other than use another app.

For Everything, it's not poor programming.

You have to remember how it works.

1) NTFS USN Journal records that a new file has
"appeared" in the file system.
2) Everything.exe reads the USN Journal, from the
current pointer, sees the new file.
3) Everything.exe writes the new file into its database.

This becomes a "loop", if you inadvertently have the
database itself in a "visible" place that Everything.exe
can index. Everything does (3), the Journal does (1),
and the thing goes around in a merry circle.

I don't think that's an actual issue, although it sounds good in theory.

I'd bet that each of us who use Everything are able to type "everything"
into its interface and see, among the results, its index file. There's
never been any noticeable looping behavior, AFAIK.

Its author probably took care of that behavior a very long time ago, in
one of the earliest versions.

--

Char Jackson