On Tue, 5 Jan 2016 17:11:41 +0100, Matthias Klumpp <matth...@tenstral.net> wrote: > Hmm, are you doing anything special with PK which could trigger this > issue, so I can reproduce it?
No, like Sam I'm just running Gnome, without even using gnome-software.
> PK itself should terminate after idling for a while, freeing any
> resources it still uses.
It's packagekitd that's using tons of RAM, isn't that a service started by
systemd?
"systemctl status packagekit" produces
● packagekit.service - PackageKit Daemon
Loaded: loaded (/lib/systemd/system/packagekit.service; static; vendor
preset: enabled)
Active: active (running) since Mon 2016-01-04 20:04:22 CET; 24h ago
Main PID: 3863 (packagekitd)
CGroup: /system.slice/packagekit.service
└─3863 /usr/lib/packagekit/packagekitd
Jan 04 20:04:22 heffalump.sk2.org systemd[1]: Starting PackageKit Daemon...
Jan 04 20:04:22 heffalump.sk2.org PackageKit[3863]: daemon start
Jan 04 20:04:22 heffalump.sk2.org systemd[1]: Started PackageKit Daemon.
on my system just now (it was booted a day ago).
> In order to debug a potential memory leak, I would first need to be
> able to reproduce it...
I was thinking of running it with valgrind...
Regards,
Stephen
pgp6uVNleuM_W.pgp
Description: OpenPGP digital signature
