! 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 !
memory leak
Status:
RESOLVED: DUPLICATE
Severity:
blocker
Product:
Xfce4-cpugraph-plugin
Component:
General

Comments

Description brian 2012-06-14 12:27:54 CEST
The current memory consumption of xfce4-cpugraph-plugin is quite high and seems to continually grow.  Currently it's at:

VmPeak:	 1234360 kB
VmSize:	 1234356 kB
VmHWM:	  735032 kB
VmRSS:	  735032 kB

I'm sure you would agree that 700MB of real memory and 1.2GB of VM is excessive for a panel applet that just reports CPU usage.  Moreover, it has grown to this value from:

VmPeak:  1229856 kB
VmRSS:   728612 kB

Only 20 minutes ago.  And as I have sat here writing this bug report:

VmPeak:	 1235384 kB
VmSize:	 1235380 kB
VmHWM:	  736160 kB
VmRSS:	  736160 kB

It's leaked some more.
Comment 1 Landry Breuil editbugs 2012-06-14 13:03:38 CEST
Can you provide more details, such as OS/distro, which display mode (leds/grid..), update interval, etc ? How long has the plugin been running ? Also, how do you measure that values ? Here it doesn't seem to leak with that insane values.. a bug in gtk/cairo ? Which versions of those do you have ?
Comment 2 brian 2012-06-14 13:36:20 CEST
(In reply to comment #1)
> Can you provide more details,

Happy to.

> such as OS/distro,

I'm using Ubuntu Precise with the packages at http://ppa.launchpad.net/xubuntu-dev/xfce-4.10/ubuntu

> which display mode
> (leds/grid..),

"Normal", Color mode "Solid".

> update interval,

"Fastest (~250ms)"

> How long has the plugin been running ?

A few days.  I did just restart it however an hour ago and when it restarted memory use was at:

VmPeak:	   40640 kB
VmSize:	   40092 kB
VmHWM:	    6720 kB
VmRSS:	    6720 kB

Currently it's at:

VmPeak:	  255088 kB
VmSize:	  255084 kB
VmHWM:	   23740 kB
VmRSS:	   23740 kB

So clearly it's growing, and I believe will continue, without bound since there is really no long-term accumulating data that should account for a continuous growth in memory consumption.

> Also, how do you measure that values ?

The above is from

$ cat /proc/$pid_of_plugin/status

> Here it doesn't seem to leak with
> that insane values..

No?  700MB of real memory for a CPU monitor plugin is not insane?  700MB is more than 100x what it starts out with which is show above at only 6.7MB.

> a bug in gtk/cairo ?

I don't know, but I don't see any evidence of anything else leaking.

> Which versions of those do you
> have ?

libcairo2: 1.10.2-6.1ubuntu3
libgtk2.0-0: 2.24.10-0ubuntu6
Comment 3 Landry Breuil editbugs 2012-06-14 14:12:05 CEST
> > Here it doesn't seem to leak with
> > that insane values..
> 
> No?  700MB of real memory for a CPU monitor plugin is not insane?  700MB is
> more than 100x what it starts out with which is show above at only 6.7MB.

Calm down. I said here on my OpenBSD system it doesn't show insane values like yours.

Here in various configurations it doesn't seem to leak so i'd be tempted to blame linux specific code in os.c, but i see nothing being allocated and not freed there... maybe the FILE*, or the cpuStr char* ? I'll look into it.
Comment 4 Landry Breuil editbugs 2012-06-14 14:16:08 CEST
Let's merge this bug with the already reported one.

*** This bug has been marked as a duplicate of bug 8521 ***

Bug #9025

Reported by:
brian
Reported on: 2012-06-14
Last modified on: 2012-06-14

People

Assignee:
Florian Rivoal
CC List:
1 user

Version

Attachments

Additional information