Tracker-miner-fs3 is using a huge amount of RAM

Ask Fedora
, ,
1

tracker-miner-fs3 is using more RAM than Google Chrome:

$ ps vax --sort=-rss  | head -n 3
    PID TTY      STAT   TIME  MAJFL    TRS      DRS    RSS %MEM COMMAND
   7365 ?        SNsl  31:14  31284     56  2183499 535280  3.2 /usr/libexec/tracker-miner-fs-3
  22500 ?        SLl    0:12    245 163613 34287239 380056  2.3 /opt/google/chrome/chrome

I had to resort to turning it off until the next package update turns it back on again:

$ sudo chmod -x /usr/libexec/tracker-miner-fs-3

Are other people seeing tracker-miner-fs3 using a huge amount of RAM?

Does anybody know if it has a memory leak?

1 Like
2

Depending upon the amount of data it has to index it may take some time and use quite a bit of memory as it builds the database. Once it has processed the list then it uses very little RAM or CPU to keep up to date.

My suggestion: find a time when you are able to let the system sit idle and just let tracker-miner do its job so it does not impact you during busy times.

3

The tracker-extract-3.service is crashing as well

tracker-extract-3.service: Failed to add control inotify watch descriptor for control group /user.slice/user-1000.slice/user@1000.service/app.slice/tracker-extract-3.service: No space left on device

The No space left on device is the perror(3) string for ENOSPC and inotify_add_watch(2) man page says it returns ENOSPC when The user limit on the total number of inotify watches was reached or the kernel failed to allocate a needed resource.

I don’t think there will ever be a time when it works on the grounds that it crashes due to a shortage of inotify watches.

4

I opened a bug report on the Gnome Gitlab web site.

1 Like