Everything using lots of RAM and freezes

[vkapadia]

I've been having this problem just recently, started probably a couple weeks ago. After a while, my computer would slow down a bunch. Looking in Task Manager, it shows Everything is using a ton of memory. It's over 1.5gb memory, it's even outstripping my 30+ Google Chrome tabs. Trying to open Everything does nothing, the window never comes up. I have to force shutdown Everything then start it back up, after which it starts indexing again. Any ideas on what I can do to find the problem?

[horst.epp]

Sorry but such a post is almost useless.
What about any information about your OS, Everything version and bitnes ?

[NotNull]

First guess:
You are running out of RAM and therefor Everything starts swapping (temporarily save parts of RAM to disk to create space for other activities). Everything is very sensitive to that as the entire Everything database is loaded in RAM.

1.5 GB RAM usage would correspond with about 15-20 million files and folders ("objects") indexed by Everything.
How many objects does Everything indicate on your system? See the left side of the status bar for that.

To check if the freezing is indeed cause by swapping, next time this occurs close Chrome instead of Everything.
That should free a lot of RAM, giving Everything more "breathing room" and solve the freeze.
(If theory is correct)


Some other questions:
- 32 or 64 bit Everything?
- Which version of Everything?
- What Windows version?
- How much RAM do ou have in your system?

[NotNull]

Sorry but such a post is almost useless.
What about any information about your OS, Everything version and bitnes ?

Sorry didn't see that when typing ..

@vkapadia: What horst.epp said

[vkapadia]

Apologies, should have mentioned.

OS: Windows 10
CPU: AMD Ryzen 7 2700x
RAM: 32GB
Everything version: 1.4.1.935 (x64)
Bitnes: i don't know what that is
Objects: 8 million

I kept Everything running since yesterday, it seems to be ok for now. When I opened it yesterday, it went up to 1.5gb ram, looks like it settled down to about 740mb now.

I'll update this if anything changes.

[horst.epp]

Apologies, should have mentioned.
...
Bitnes: i don't know what that is
...

I should have written bitness and not bitnes.
Bitness is the definition of what OS version you have, x86 (32bit) or x64 (64bit)

[vkapadia]

Ah lol. 64 bit Windows 10, running 64 bit Everything.

[therube]

And what options are enabled in; Tools | Options | Indexes ?

[vkapadia]

Index recent changes
Index file size
Fast size sort
Index date modified
Fast date modified sort
Fast path sort

[NotNull]

First guess:
You are running out of RAM

RAM: 32GB

Well, it looks like that first guess is off the table ..
Keep us posted if this happens again.

[vkapadia]

Yeah this is a nicely spec'ed computer, just built it this past summer. Doubt it has memory issues. I tried to unlock my computer this morning and it was stuck (the login screen took my pin but kept spinning). I had to reboot. Not sure if it was related to the Everything memory issue. Things seem fine for now, will keep an eye on it.

[NotNull]

Just a thought (second guess ):

Consider running a memory testing program like Memtest86. It might be a hardware issue.

[therube]

I tried to unlock my computer this morning and it was stuck (the login screen took my pin but kept spinning).

I've had that any number of times of late (on a piece of crap Win10 system - not mine) when I've tried to log in under a second user account name.

Computer is asleep.
Wake it up.
Select user account.
Enter password.

& that's it. Sits there doing nothing. Have to do a hard shutdown & restart.


(In my case, pretty sure Everything is not the issue. I'd look at crap 10.)

[vkapadia]

Yeah I know the login screen issue was not Everything. I just mentioned it because that's the reason I had to reboot. This morning, logged in just fine, but pc was going slow. Lo and behold, Everything was stuck again. Screenshot of Everything window and Task Manager is below. I couldn't even paste the screenshot into Paint until I killed Everything.

I'll run memtest and see what I get.

Screenshot:

everything.png (57.77 KiB) Viewed 13040 times

[void]

Could you please try running Everything in debug mode:

• In Everything, type in the following search and press ENTER:
  /debug

Wait for Everything to freeze again.
What is shown in the debug console?

[vkapadia]

Ok, started debug mode. Will report back if it freezes. Thanks!

[therube]

Your Ryzen is 8 core, so 7.7% is close to 100% CPU, for 1 core?

And Everything & bztransmit & antimalware are all using (close to) 1 core, each?

Are your files store in the cloud (blackblaze) rather then locally?

[vkapadia]

@therube my files are local, bztransmit just backs them up to cloud. Here's the screenshot for task manager this morning, shows only Everything doing much, taking over 5gb ram!

everything3.png (34.98 KiB) Viewed 13025 times

[vkapadia]

Also, Resource Monitor shows all cores being used a little, no one core is at 100%.

[vkapadia]

@void here is a screenshot of the debug window, whole buffer is pasted at https://paste.ee/p/SuuiE

everything2.png (47.47 KiB) Viewed 13024 times

[void]

Thanks for the logs.

Everything might be taking a long time to process many changes.

Have you noticed, when Everything hangs, does the memory usage keep growing?

Could you please try running Everything in verbose debug mode:

• In Everything, type in the following search and press ENTER:
  /debug
• Type in the following search and press ENTER:
  /verbose

Wait for Everything to freeze again.
What is shown in the debug console?
verbose mode should show more detailed log of what Everything is processing..

[vkapadia]

@void

Yes, it keeps growing. This morning it was almost 7gb. I'll run in verbose and report back. Thanks for helping out!

[vkapadia]

This morning again around 7gb memory. Here's the verbose log. https://paste.ee/p/ZCq8x

[vkapadia]

Looks like all those images its trying to index are Plex video thumbnails. I've excluded the Plex data folder from indexing. Let's see if that helps. I've kept verbose debug running just in case.

[void]

Thanks for the verbose debug logs.

There are thousands of entries of Everything updating Find Data for image files that have been modified.
It doesn't explain the high memory usage, even if there are millions of file changes.

Please let me know if excluding the plex data folder helps.

Please consider disabling extended information cache monitor and disabling size and date modified indexing.
With these disabled, Everything will no longer process files that have been modified:

• In Everything, from the Tools menu, click Options.
• Click Index on the left.
• Uncheck Index file size.
• Uncheck Index date created.
• Uncheck Index date modified.
• Uncheck Index date accessed.
• Uncheck Index attributes.
• Click OK.
• In Everything, type in the following search and press ENTER:
  /extended_information_cache_monitor=0

[vkapadia]

Been running for several days now with no issues. I unchecked those options anyway, just to help performance. Thanks so much!