Created attachment 1522721 [details] Screenshot of top Description of problem: I noticed a massive wave of swap IO, when another process started, that used to use 1gb of ram and my system stood still iowise. So i took "top" to check and sorted for memoryusage and found gnome-software to use up 11+ gb vmem and ~9-10 gb real memory. See Screenshot Gnome-Software was not even started by me. It just was on. As soon as i killed it, 10g memory was cleared. /v/l/messages has this to offer: Jan 23 10:35:31 eve dbus-daemon[1600]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.186' (uid=1000 pid=2933 comm="/usr/bin/gnome-software --gapplication-service " label="unconfined_u:unconfined_r:unc onfined_t:s0-s0:c0.c1023") --- Reboot --- at 14:29... Jan 23 14:29:38 eve dbus-daemon[1133]: [system] Activating via systemd: service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.190' (uid=1000 pid=2462 comm="/usr/bin/gnome-software --gapplication-service " label="unconfined_u:unconfined_r:unconfined_t: s0-s0:c0.c1023") Question A: what happended here exactly? Question B: why does gnome-softwarecenter run in an invisible form in the background? it is a desktop app. And btw, I do not use gnome-shell, I run cinnamon . But: root 1457 0.0 0.0 406972 880 ? Ssl 14:29 0:00 /usr/sbin/gdm root 1468 0.0 0.0 381404 1036 ? Sl 14:29 0:00 \_ gdm-session-worker [pam/gdm-launch-environment] gdm 1483 0.0 0.0 423564 632 tty1 Ssl+ 14:29 0:00 | \_ /usr/libexec/gdm-x-session gnome-session --autostart /usr/share/gdm/greeter/autostart root 1485 0.0 0.0 288524 11704 tty1 Sl+ 14:29 0:02 | \_ /usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -background none -noreset -keeptty -verbose 3 gdm 1578 0.0 0.0 669564 1832 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart gdm 1598 0.0 0.3 3967820 53208 tty1 Sl+ 14:29 0:04 | \_ /usr/bin/gnome-shell gdm 1745 0.0 0.0 462044 920 tty1 Sl 14:29 0:00 | | \_ ibus-daemon --xim --panel disable gdm 1748 0.0 0.0 387044 924 tty1 Sl 14:29 0:00 | | \_ /usr/libexec/ibus-dconf gdm 1911 0.0 0.0 313224 872 tty1 Sl 14:29 0:00 | | \_ /usr/libexec/ibus-engine-simple gdm 1786 0.0 0.0 611268 1116 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-xsettings gdm 1788 0.0 0.0 386164 848 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-a11y-settings gdm 1789 0.0 0.0 459376 1112 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-clipboard gdm 1790 0.0 0.0 717388 2364 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-color gdm 1793 0.0 0.0 466768 820 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-datetime gdm 1794 0.0 0.0 390008 540 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-housekeeping gdm 1795 0.0 0.0 609252 1112 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-keyboard gdm 1802 0.0 0.0 1056208 2048 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-media-keys gdm 1804 0.0 0.0 309712 0 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-mouse gdm 1808 0.0 0.0 624756 1884 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-power gdm 1816 0.0 0.0 382856 0 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-print-notifications gdm 1819 0.0 0.0 309728 0 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-rfkill gdm 1820 0.0 0.0 383444 900 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-screensaver-proxy gdm 1825 0.0 0.0 407900 672 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-sharing gdm 1831 0.0 0.0 569168 0 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-smartcard gdm 1832 0.0 0.0 450936 796 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-sound gdm 1833 0.0 0.0 544300 1116 tty1 Sl+ 14:29 0:00 | \_ /usr/libexec/gsd-wacom root 1944 0.0 0.0 404232 1860 ? Sl 14:29 0:00 \_ gdm-session-worker [pam/gdm-password] marius 1977 0.0 0.0 423564 476 tty2 Ssl+ 14:29 0:00 \_ /usr/libexec/gdm-x-session --run-script cinnamon-session-cinnamon root 1982 1.9 0.7 603868 124060 tty2 Sl+ 14:29 2:38 \_ /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 marius 2006 0.0 0.0 590992 5128 tty2 Sl+ 14:29 0:00 \_ cinnamon-session --session cinnamon marius 2161 0.0 0.0 29028 36 ? Ss 14:29 0:00 \_ /usr/bin/ssh-agent /bin/sh -c exec -l /bin/bash -c "cinnamon-session-cinnamon" Something serious got wrong here. Version-Release number of selected component (if applicable): gnome-software-3.28.2-4.fc28.x86_64
Same situation here. It used 17.7gb in my case. https://i.imgur.com/4iwXW45.png
This problem still persists and drives me nuts. gnome-software occassionally gets into memory leak mode while checking for updates, then crashes. I can't report it in ABRT because although a huge 2Gb coredump is generated, the software is unable to process it: --- Running report_uReport --- Hiba: No segments found in coredump './coredump' I have uploaded the ZIP to FAF at https://retrace.fedoraproject.org/faf/dumpdirs/new/ccpp-2019-03-12-09:03:41.999449-2332.tar.gz
"ups, it did it again." gnome-software-3.28.2-4.fc28.x86_64
"ups, it did it again." this bug is provided to you by .... packagekit !
That's OK, the question is how we could debug it to get a fix upstream.
the two last manifestations of this bug where caused by packagekit. A few months ago, i have read,that packagekit will be retired. On the other hand, when we know what packagekit does with gnome-software ( i guess alerting it for updates ), maybe we can force the bug to happen.
For those who wonder, this may be the source of retiring PackageKit: https://blogs.gnome.org/hughsie/2019/02/14/packagekit-is-dead-long-live-well-something-else/ It's a mess, reading the comments. Anyway, I posted some fresh logs to the GNOME Gitlab about the same memory leak: https://gitlab.gnome.org/GNOME/gnome-software/issues/486#note_485314
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.
Today: 26335.040806] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/session-2.scope,task=gnome-software,pid=2532,uid=1000 [26335.040812] Out of memory: Kill process 2532 (gnome-software) score 585 or sacrifice child [26335.040832] Killed process 2532 (gnome-software) total-vm:15827240kB, anon-rss:7983884kB, file-rss:0kB, shmem-rss:1016kB the swap from this amount of io collapsed the system for a while. Version: 3.28.2-5
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.