[BUG] Index file content uses up all memory when no Include/exclude file masks present - i.e. index ALL content

Discussion related to "Everything" 1.5 Alpha.
Post Reply
Deipotent
Posts: 4
Joined: Thu Nov 04, 2021 12:27 pm

[BUG] Index file content uses up all memory when no Include/exclude file masks present - i.e. index ALL content

Post by Deipotent »

As title - For some reason I had removed all file masks from include/exclude files boxes, and with Index file content option enabled, Everything ends up using up all memory really quickly (I have 40GB RAM and it shoots up to 26 GB within a few seconds).

I assume that have no file masks in include/exclude files means it will attempot to index literally everything.
Deipotent
Posts: 4
Joined: Thu Nov 04, 2021 12:27 pm

Re: [BUG] Index file content uses up all memory when no Include/exclude file masks present - i.e. index ALL content

Post by Deipotent »

Just read the caveat under Content Indexing post...
Everything will keep content in memory.
Content indexing is intended for indexing user documents only.
I do not recommend indexing over 1GB of text.
For the best performance, set an include only folder.
Still don't think Everything should run-away with memory usage and end up causing system instability though.
horst.epp
Posts: 1430
Joined: Fri Apr 04, 2014 3:24 pm

Re: [BUG] Index file content uses up all memory when no Include/exclude file masks present - i.e. index ALL content

Post by horst.epp »

Ignoring every warning and configuration help is just a simple user error.
Catching all such stupid errors waste a lot of programming resources.

Nevertheless, Everything should have some configurable memory limit with a default.
therube
Posts: 4879
Joined: Thu Sep 03, 2009 6:48 pm

Re: [BUG] Index file content uses up all memory when no Include/exclude file masks present - i.e. index ALL content

Post by therube »

How about Help | Troubleshooting Information & Tools | Debug -> Statistics.
mariamatcha
Posts: 6
Joined: Tue Mar 05, 2024 2:27 pm

Re: [BUG] Index file content uses up all memory when no Include/exclude file masks present - i.e. index ALL content

Post by mariamatcha »

horst.epp wrote: Fri Jun 14, 2024 9:24 am Ignoring every warning and configuration help is just a simple user error.
Catching all such stupid errors waste a lot of programming resources.

Nevertheless, Everything should have some configurable memory limit with a default.
This :)
Post Reply