Open Navy-Ro opened 3 days ago
Can you try running:
NEMO_DEBUG=Search nemo --debug
and try to see if it ends up in any unexpected locations.
There are checks to try and keep the search from getting redirected into places like /dev, /proc, etc... but this is what it sounds like may be happening.
Ref: https://github.com/linuxmint/nemo/issues/3258 https://github.com/linuxmint/nemo/commit/0a391ab5914817e57da8915676dde20a2c87bd7b
Tried to reproduce this with a content search for 'abc' in my home directory. Took 4m 30secs - over about 60,000 files, with other apps running without any problems.
total used free shared buff/cache available
Mem: 31Gi 3.2Gi 23Gi 28Mi 5.2Gi 27Gi
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 !