-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nemo content search - fills all ram #3472
Comments
Tried to reproduce this with a content search for 'abc' in my home directory.
|
! Strange behavior in Debug mode, no error, no fully locked pc, |
Hi, searched again and looked at every file it stopped/paused to find those files were broken/corrupted. |
Strange - are those old MS Word .doc files? Do you have others of that format that are searched successfully? We use a 3rd party program (catdoc) to content search that file type, I wonder if that was what's failing. Are those files gone completely? Maybe you could just run Either way, glad you got it resolved |
yes, old MS Word .doc files, i tottaly deleted that files on this pc, |
Distribution
current LMDE6 & Ubu - LM22
Package version
6.2.9 on both
Graphics hardware in use
Lmde: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] & /Ubu: an old amd saphire
Frequency
Always
Bug description
Hi, every time i do a (personal number) Content Search with Nemo in Home directory or Docs (no other apps runing) the RAM starts to fill up to maximum till PC stops responding. (it also happened in previsious versions LM & LMDE - than i used recoll wich i dont prefer)
!
(in the screen capture below i closed Cinnamon before it locked my pc)
Captură de ecran din 2024-10-19 03-29-40
Steps to reproduce
simply do a Content Search with Nemo in Home directory - too much files maybe ? :)
Expected behavior
--
Additional information
maybe an Optional file indexer AddOn / Nemo (like tracker/baloo) - would be better for someone managing lots of docs/files.
Thank u all LM Team !
The text was updated successfully, but these errors were encountered: