/usr/libexec/tracker-miner-fs consumes high cpu time /usr/libexec/tracker-store uses up all available memory causing the system to be nearly unresponsive and the and the system started killing off apps due to running out of memory. Reproducible: Always Unfortunatley, by the time I realized there was a problem the system was starting to run from swap. Last I saw, tracker-store was at 1.6G memory, tracker-miner-fs was using 90%cpu. After the crash and recovery, evolution, one desktop, several webpages in chromium and apparently tracker-store were killed off. Tracker-store was running again, but at a small memory usage and growing, with tracker-miner-fs still running. It eventually finished and went back to sleep. tracker-store is currently at 296MB virt. mem., 42.5MB resident mem. Tracker-miner-fs is using 1.0GB virt., 717.8MB resident memory.
total system memory is 4G actual + 1G swap. Start times indicate they have been running 2.5 days.
Created attachment 297097 [details] emerge --info emerge --info app-misc/tracker
Please try tracker-0.12.9, it contains fixes for several memory leaks. If the leak still exists in 0.12.9, please file a bug upstream (https://bugzilla.gnome.org/enter_bug.cgi?product=tracker), and add gnome@gentoo.org to the upstream bug's CC list. Try to determine whether a specific file or set of files in the indexed directories is causing tracker-miner-fs's memory usage to blow up. You can get an idea of what tracker-miner-fs is doing with the following commands: $ tracker-control --kill=miners $ /usr/libexec/tracker-miner-fs --no-daemon --verbosity=3
Memory consumption had climbed for store and miner-fs by the time I upgraded. OK, I could not find 0.12.9 in any overlays, so I bumped the 0.12.8 ebuild unchanged in my local overlay. It installed fine, and seems to run much better, faster. But that could be due to the fact it hasn't stuffed system memory into running from swap (yet). I even moved the ~.cache/tracker directory so things would start from scratch. After the initial run, I restarted the miner without the --no-daemon switch so it is running still in the terminal with debug output. Initial post run info: store 306.8MB virt, 77.4MB resident tracker-miner-fs 206.4MB virt, 8.5MB resident I'll see what it is like in the morning. Nearly bedtime for me and I have to work the rest of the week.
(In reply to comment #4) > OK, I could not find 0.12.9 in any overlays http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-misc/tracker/tracker-0.12.9.ebuild?view=log
I had re-synced, but it obviously had not propagated itself to the mirror I got from the rotation. I do not have a cvs checkout of the tree yet. Anyway, so far this morning all is looking fine. I deleted a couple files this morning and the store has actually dropped a tiny bit of resident memory.
OK, 0.12.9 is not giving me any memory leak problems. It has been running for nearly a week without issue. I would consider this bug closed if 0.12.8 was removed from the tree in favor of 0.12.9. Thank you.
(In reply to comment #7) Good to hear. However, I would prefer to keep two different 0.12.x releases in the tree, in case the new version might have introduced regressions. (Of course, 0.12.8 will *not* be considered a candidate for stabilization.) If 0.12.9 starts misbehaving, please reopen.
