I don't know if it is maybe too early to notice this or maybe not the best place to do so, but I wanted to warn Gentoo developers to not stabilize this version (when that time comes) until the issue https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/302 is fixed as it has severe memory leaks that should be addressed before.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e828d1ed696ea6474dfe584df3aa45060bc99c32 commit e828d1ed696ea6474dfe584df3aa45060bc99c32 Author: Guillermo Joandet <gjoandet@gmail.com> AuthorDate: 2024-08-06 01:51:13 +0000 Commit: Pacho Ramos <pacho@gentoo.org> CommitDate: 2025-01-15 17:29:48 +0000 gnome-extra/gnome-system-monitor: Bump to 47.0 Bug: https://bugs.gentoo.org/937631 Closes: https://bugs.gentoo.org/937539 Signed-off-by: Guillermo Joandet <gjoandet@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/38647 Signed-off-by: Pacho Ramos <pacho@gentoo.org> gnome-extra/gnome-system-monitor/Manifest | 1 + .../gnome-system-monitor-47.0.ebuild | 55 ++++++++++++++++++++++ 2 files changed, 56 insertions(+)
Are you still hitting this with 47 version? If still the case, I would try to locally test with versions between 45 and 46, to try to find the commit causing this issue https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/blob/main/NEWS?ref_type=heads#L38 Thanks
(In reply to Pacho Ramos from comment #2) > Are you still hitting this with 47 version? If still the case, I would try > to locally test with versions between 45 and 46, to try to find the commit > causing this issue > https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/blob/main/ > NEWS?ref_type=heads#L38 > > Thanks I've ran a quick test with version 47 leaving it running for 2.5 hours with this result (according to htop) with the following RAM usages (total in a running system). Total RAM usage after start: 3.66GB Ram usage after 2.5h: 4.04GB Ram usage after close: 3.66GB While there are about 400MB in usage which seems too much I do not observe any major impact on memory leaks so I think this can be marked as fixed. Thanks.
