! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Slow memory leak
Status:
RESOLVED: FIXED
Product:
Xfce4-hardware-monitor-plugin
Component:
General

Comments

Description User 2019-02-09 14:58:36 CET
I have one instance showing CPU usage, and two other instances showing network usages for two network interfaces. I can see that after a few days, each instance's memory usage increases, so much so that I now have a cron job restart the panel every night. Please let me know what I can do to help debug this. I am using 1.6.0, but it also happened in 1.5.0, and maybe 1.4.0.
Comment 1 OmegaPhil 2019-02-09 15:45:11 CET
From the readme:

==============================================

libgnomecanvas (which libgnomecanvasmm binds) has a stupid memory leak
in its paint routine, which I have reported:

My bug: https://github.com/OmegaPhil/hardware-monitor-applet/issues/5
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753621
GNOME bug: https://bugzilla.gnome.org/show_bug.cgi?id=729717

In both cases the bug has been ignored. Running the plugin for days will
gradually cause the RSS to increase without limit - for Debian users I
have produced fixed i386 and amd64 Debian archives -
https://github.com/OmegaPhil/libgnomecanvas/tree/pkg

==============================================

This is now out of date, the Debian package finally took on my patch recently - however I have stopped virtually all my computing work about half a year ago, so I don't have any plans updating this plugin currently etc.

After upgrading the relevant package, would be interesting to see if you still have the issue.
Comment 2 User 2019-02-09 16:05:04 CET
Dang, my own fault for not reading the readme. Thanks, OmegaPhil. I don't use Debian but I've applied your patch locally to the relevant Slackware package.
Comment 3 OmegaPhil 2019-02-09 16:17:07 CET
Tell me how you get on.
Comment 4 User 2019-02-09 16:20:57 CET
I'll report back after a week or so, thanks.
Comment 5 User 2019-02-16 17:03:45 CET
That definitely appears to have fixed it. Thanks.

Bug #15131

Reported by:
User
Reported on: 2019-02-09
Last modified on: 2019-02-16

People

Assignee:
OmegaPhil
CC List:
0 users

Version

Version:
unspecified

Attachments

Additional information