Hello,
First I'd like to thank the creator of such an awesome program, I really love it and couldn't live without it. A million thanks for keeping updating it and adding key features like sessions, which helped me a lot
Now the problem I'm facing is that over time Everything decides to eat all my ram and fill up the pagefile as well until my system crashes.
I don't understand its behaviour because yes, I have dozens of tabs opened at the same time, but without opening more or even interacting at all with the program for a while, the program starts to consume more and more ram, from 15-30gb (it increases over time, but slowly for a while) to all of it and even a lot from a pagefile of more than 100GB (specially huge for Everything to last longer before making the system crash).
I don't know if it eats all of the available pagefile or just an enough amount to make the system unable to handle it and lead to a crash. Honestly, I don't know if this is possible. What I've seen is that when the free ram is close or lower than 1GB and I check the pagefile usage, the amount in use is about a 40-50% of the total available. But then I quit from Everything, so I don't know how much it ends consuming until the crash happens. After closing Everything up to 40GB of ram are recovered. Then restoring the previous session leaves the system with around 20-25GB of free ram. It keeps using a similar amount for a few hours, until suddenly the above mentioned happens, and if I'm not paying attention it ends up in the system crashing due to the system getting out of ram.
It has also a CPU usage of more than a 15%, is this normal?
I'm sitting on a 64GB system and without Everything running the normal consumption can reach around 30GB due to other programs running.
DB size is only 1.5GB.
To add just something I've noticed is that the only property I have set (lenght) takes a lot to get updated, and it does it in bulks, not in real time as new files are stored but in a long process at a certain moment. I think in that process it consumes more ram. Is this the expected behaviour? any way to make it update that attribute in real time?
Screenshot taken short after starting Everything. I'll add others later as it keeps using more resources.
Huge RAM leakage leading to a system crash + high CPU consumption.
Huge RAM leakage leading to a system crash + high CPU consumption.
Last edited by void on Fri Nov 22, 2024 10:39 pm, edited 2 times in total.
Reason: fixed image
Reason: fixed image
Re: Huge RAM leakage leading to a system crash + high CPU consumption.
None of what you say is "normal".
Your screenshot (since it doesn't show up), https://ibb.co/6v4pHRq.
(That's a lot of RAM .)
What version of Everything? [1.5.x ?]
How many files are we dealing with?
Aside from indexing just these files, are you also indexing any file Properties (if using 1.5)? [Length]
Post, Help | Troubleshooting Information.
Your screenshot (since it doesn't show up), https://ibb.co/6v4pHRq.
(That's a lot of RAM .)
What version of Everything? [1.5.x ?]
How many files are we dealing with?
Aside from indexing just these files, are you also indexing any file Properties (if using 1.5)? [Length]
Post, Help | Troubleshooting Information.
Re: Huge RAM leakage leading to a system crash + high CPU consumption.
Version 1.5.0.1383a (x64)
The total amount is around 25M, mostly are empty folders (I need to keep this folders tree). Time ago the total amount reached more than 100M (99% empty folders) and I had not this issue. It indeed used to use a lot of ram, but I don't remember it eating all the free RAM + Pagefile until making the system crash. I had then a 15-30GB .db, but it used to take a lot of time at each start for the program to be usable.
About the properties, only Length is being indexed.
Thank you for fixing the image
Now my index settings looks like this:
At some point I'd like to recover the +100M tree folder structure but I'm scared it won't be possible not even doubling the RAM if the Everything's voracity persists
The total amount is around 25M, mostly are empty folders (I need to keep this folders tree). Time ago the total amount reached more than 100M (99% empty folders) and I had not this issue. It indeed used to use a lot of ram, but I don't remember it eating all the free RAM + Pagefile until making the system crash. I had then a 15-30GB .db, but it used to take a lot of time at each start for the program to be usable.
About the properties, only Length is being indexed.
Thank you for fixing the image
Now my index settings looks like this:
At some point I'd like to recover the +100M tree folder structure but I'm scared it won't be possible not even doubling the RAM if the Everything's voracity persists
Re: Huge RAM leakage leading to a system crash + high CPU consumption.
Are you indexing content?
Please try disabling content indexing under Tools -> Options -> Content.
Please try disabling content indexing under Tools -> Options -> Content.
Re: Huge RAM leakage leading to a system crash + high CPU consumption.
Nope, that option is already disabled.
Re: Huge RAM leakage leading to a system crash + high CPU consumption.
I've been thinking and indeed when I had +100M folders sometimes the program was using a lot of ram + pagefile, just to free it up both after a while. Sometimes closing some other apps first, I don't remember if just to speed up the process or as a requirement for it to happen. I used to do this because how slow was to get the program ready after closing it. Now it's almost instant so I can restart it when I notice the leakage. The problem is when I don't notice it. Many times I leave the PC unattended for 10-20 minutes, I come back just to find the system has crashed. Checking the events viewer it says the system got out of virtual/memory.Turok wrote: ↑Fri Nov 22, 2024 11:33 pm Version 1.5.0.1383a (x64)
The total amount is around 25M, mostly are empty folders (I need to keep this folders tree). Time ago the total amount reached more than 100M (99% empty folders) and I had not this issue. It indeed used to use a lot of ram, but I don't remember it eating all the free RAM + Pagefile until making the system crash. I had then a 15-30GB .db, but it used to take a lot of time at each start for the program to be usable.
About the properties, only Length is being indexed.
Thank you for fixing the image
Now my index settings looks like this:
At some point I'd like to recover the +100M tree folder structure but I'm scared it won't be possible not even doubling the RAM if the Everything's voracity persists
Re: Huge RAM leakage leading to a system crash + high CPU consumption.
Please send your Help -> Troubleshooting Information in a bugreport
For 100 million folders, I would expect Everything to use around 10GB of RAM.
For 100 million folders, I would expect Everything to use around 10GB of RAM.
Re: Huge RAM leakage leading to a system crash + high CPU consumption.
Thanks for the Help -> Troubleshooting Information.
Your setup looks OK.
This will prefetch 2000 thumbnails.
To change this setting:
request_extra_fileinfo_end
Could you please send your Tools -> Debug -> Statistics in a bugreport
Your setup looks OK.
This setting could be causing trouble.request_extra_fileinfo_end=2000
This will prefetch 2000 thumbnails.
To change this setting:
- In Everything 1.5, from the Tools menu, click Options.
- Click the Advanced tab on the left.
- To the right of Show settings containing, search for:
extra - Select: request_extra_fileinfo_end
- Set the value to: 0
(0 is the default) - Click OK.
request_extra_fileinfo_end
Could you please send your Tools -> Debug -> Statistics in a bugreport