Description of problem: The process tracker-store leaks GBs of memory when running, in my case it was ~10GB in twelve hours. Version-Release number of selected component (if applicable): tracker-2.1.0-1.fc28.x86_64 Additional info: The fix is available upstream, please see the commit: https://gitlab.gnome.org/GNOME/tracker/commit/990bde3809368983b77bc7c1c9a3bb7242d5933c
I second that. Downgrading to 2.0.3 eliminates the problem in the meanwhile.
Can confirm, woke up this morning to tracker-store consuming 3.2GB of resident memory. But I'm running this slightly newer version, which was installed yesterday, tracker-2.1.1-1.fc28.x86_64 I killed the offending user's tracker-store process and it seems to be behaving now.
(In reply to Steeve McCauley from comment #2) > Can confirm, woke up this morning to tracker-store consuming 3.2GB of > resident memory. But I'm running this slightly newer version, which was > installed yesterday, > > tracker-2.1.1-1.fc28.x86_64 > > I killed the offending user's tracker-store process and it seems to be > behaving now. 2.1.1 seems to fix it for me. Are you sure you've restarted the daemon since the update?
(In reply to Dmitry Burstein from comment #3) > (In reply to Steeve McCauley from comment #2) > > Can confirm, woke up this morning to tracker-store consuming 3.2GB of > > resident memory. But I'm running this slightly newer version, which was > > installed yesterday, > > > > tracker-2.1.1-1.fc28.x86_64 > > > > I killed the offending user's tracker-store process and it seems to be > > behaving now. > > 2.1.1 seems to fix it for me. Are you sure you've restarted the daemon since > the update? I run 2.1.1-1 and it leaks A LOT. In a 24 hour period (laptop hibernated overnight - didn't reboot), I was OOM/Trashing with 32GB of memory - all due to Tracker (2.1.1-1 is the current version). This has been an issue through out most of the F28 install time. I've been looking for ways to document/dump stuff for a BZ. Any advice?
I'm running tracker.x86_64 version 2.1.0-1.fc28 OOM Killer just ran: [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name [24360] 1000 24360 4986588 3626624 39010304 1196502 0 tracker-store rss: 3626624 * 4096 / 1024. / 1024. / 1024. = 13.8 GB
same Problem Fedora WorkStation 30 tracker-2.2.1-1.fc30.x86_64 tracker-miners-2.2.1-1.fc30.x86_64 journalctl log, I do not know if this information is helpful. Mar 28 14:21:02 localhost.localdomain tracker-store[2231]: OK Mar 28 15:20:55 localhost.localdomain tracker-store[10554]: Source ID 2 was not found when attempting to remove it Mar 28 15:20:55 localhost.localdomain tracker-store[10554]: OK Mar 28 15:20:59 localhost.localdomain audit[12188]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=8 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12188 comm="pool-tracker-st" exe="/usr/libexec/tracker-store" sig=11 res=1 Mar 28 15:21:04 localhost.localdomain audit[12360]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=8 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12360 comm="pool-tracker-st" exe="/usr/libexec/tracker-store" sig=11 res=1 Mar 28 15:21:09 localhost.localdomain audit[12476]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=8 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12476 comm="pool-tracker-st" exe="/usr/libexec/tracker-store" sig=11 res=1 Mar 28 15:21:13 localhost.localdomain audit[12501]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=8 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12501 comm="pool-tracker-st" exe="/usr/libexec/tracker-store" sig=11 res=1 Mar 28 15:21:17 localhost.localdomain audit[12559]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=8 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12559 comm="pool-tracker-st" exe="/usr/libexec/tracker-store" sig=11 res=1 Mar 28 15:21:48 localhost.localdomain tracker-store[12601]: OK Mar 28 15:25:27 localhost.localdomain tracker-store[14165]: OK -- Reboot -- Mar 28 20:09:49 localhost.localdomain tracker-store[3547]: Received signal:15->'Terminated' Mar 28 20:09:49 localhost.localdomain tracker-store[3547]: OK -- Reboot -- Mar 29 14:43:20 localhost.localdomain tracker-store[4501]: OK Mar 29 14:44:57 localhost.localdomain tracker-store[4574]: OK Mar 29 15:43:24 localhost.localdomain tracker-store[7600]: OK Mar 29 15:51:43 localhost.localdomain tracker-store[8119]: OK -- Reboot -- Mar 30 07:13:23 localhost.localdomain tracker-store[3585]: OK Mar 30 07:14:54 localhost.localdomain tracker-store[4994]: Received signal:15->'Terminated' Mar 30 07:14:54 localhost.localdomain tracker-store[4994]: OK -- Reboot -- Mar 30 07:21:58 localhost.localdomain tracker-store[4407]: OK Mar 30 07:22:58 localhost.localdomain tracker-store[4521]: OK Mar 30 07:29:20 localhost.localdomain tracker-store[5027]: OK Mar 30 07:30:40 localhost.localdomain tracker-store[5450]: OK Mar 30 07:39:47 localhost.localdomain tracker-store[5523]: Received signal:15->'Terminated' Mar 30 07:39:47 localhost.localdomain tracker-store[5523]: OK Mar 30 07:42:42 localhost.localdomain tracker-store[17457]: OK Mar 30 07:43:00 localhost.localdomain tracker-store[17692]: Received signal:15->'Terminated' Mar 30 07:43:00 localhost.localdomain tracker-store[17692]: OK -- Reboot -- Mar 30 07:47:46 localhost.localdomain tracker-store[2093]: OK Mar 30 07:51:08 localhost.localdomain tracker-store[4182]: OK Mar 30 14:30:00 localhost.localdomain tracker-store[6762]: Received signal:15->'Terminated' Mar 30 14:30:00 localhost.localdomain tracker-store[6762]: OK
screenshot https://gitlab.com/youcefsourani/screenshots/blob/master/Screenshot_from_2019-03-30_14-29-34.png
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.