GNOME Bugzilla – Bug 784229
gnome-software + packagekitd using ~170M of RAM idling
Last modified: 2018-01-24 17:38:15 UTC
This is maybe related to bug #783662 but I see often after boot gnome-software process and packagekitd running in the background using which I consider a lot of memory while idle. This is case when I never started it during this session and also have no updates checking enabled (which is why I think this could be related to that bug report). My system currently has 5901M memory reported by 'free -m' and after 4h of uptime packagekitd and gnome-software still running: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND bgrubic 2318 0.0 1.5 1111172 95144 tty2 Sl+ 17:18 0:02 \_ /usr/bin/gnome-software --gapplication-service root 1654 0.3 2.2 950220 135628 ? Ssl 17:17 0:50 /usr/libexec/packagekitd Running: PackageKit-1.1.6-2.fc26.x86_64 gnome-software-3.24.3-1.fc26.x86_64 Is there a way I can provide more information? Thanks.
I upgraded to f27 now (gnome 3.26.x), I'm still seeing this behaviour with: gnome-software-3.25.91-1.fc27.x86_64 PackageKit-1.1.7-1.fc27.x86_64 Without any action on boot, both services are running and using: packagekitd: ~157MB gnome-software: ~44MB Is it possible to get any more information so you can figure out why this is using so much memory. Thanks.
How are you measuring the ram usage?
Two ways: Output of 'ps aux' gives RAM% and gnome system monitor displaying "Memory" column. If there is any better accurate way, please let me know. Thanks.
Small update, first I made a mistake with a field name of 'ps' it's %MEM, not %RAM, which represents resident memory. Second, it seems that this memory usage doesn't happen always, currently after boot gnome-software still usese ~44M, but packagekitd ~3.5M, I'm not sure why, but I guess it is related to metadata download, after boot this time it didn't download any metadata (possibly still valid) and that is why memory is still low?
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-software/issues/191.