Bug#343698: [Pkg-xfce-devel] Bug#343698: xfce4-cpufreq-plugin: Causes xfce4-panel to eat an always increasing amount of RAM

2005-12-18 Thread Stefan Ott
On Sat, Dec 17, 2005 at 12:28:56PM +0100, Roberto Pariset wrote:

 If I monitor with `top' the %MEM field of xfce4-panel, I see that
 normally it uses about 1.3 or 1.4. When I add cpufreq-plugin the
 consumption gets much higher; for instance now, after 1 day, it's
 already 17.6. It keeps increasing with time, until I can launch 
 no new programs as fork fails, since both ram and swap are filled.
 Actually running sid on amd64.

Hi

I just monitored the plugin for about 18 hours and memory usage stayed
at 1.8 the whole time so I cannot reproduce this issue (on i386).

Are you sure it's the cpufreq plugin? Can anyone using an amd64 system
reproduce this?
-- 
Stefan Ott
http://www.desire.ch/


signature.asc
Description: Digital signature


Bug#343698: [Pkg-xfce-devel] Bug#343698: xfce4-cpufreq-plugin: Causes xfce4-panel to eat an always increasing amount of RAM

2005-12-18 Thread Roberto Pariset
Stefan Ott ha scritto:
 On Sat, Dec 17, 2005 at 12:28:56PM +0100, Roberto Pariset wrote:
 
 
If I monitor with `top' the %MEM field of xfce4-panel, I see that
normally it uses about 1.3 or 1.4. When I add cpufreq-plugin the
consumption gets much higher; for instance now, after 1 day, it's
already 17.6. It keeps increasing with time, until I can launch 
no new programs as fork fails, since both ram and swap are filled.
Actually running sid on amd64.
 
 
 Hi
 
 I just monitored the plugin for about 18 hours and memory usage stayed
 at 1.8 the whole time so I cannot reproduce this issue (on i386).
 
 Are you sure it's the cpufreq plugin? Can anyone using an amd64 system
 reproduce this?

It seems it's NOT reproducible either on i386 or on ppc (Emanuele
Rocca and Yves-Alexis Perez checked).
Other than that I know of no ways to check that this problem is
actually caused by cpufreq plugin. All I can say is that if I add it
the memory keeps growing, and if I remove it then it stops. The
problem could be elsewhere, but it doesn't happen with other plugins.
Hence I think it's a cpufreq plugin issue.
If you know of any way I could run it in valgrind or something like
that please inform me :)

All the best,
Roberto


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#343698: xfce4-cpufreq-plugin: Causes xfce4-panel to eat an always increasing amount of RAM

2005-12-17 Thread Roberto Pariset
Package: xfce4-cpufreq-plugin
Version: 0.1-1
Severity: important

If I monitor with `top' the %MEM field of xfce4-panel, I see that
normally it uses about 1.3 or 1.4. When I add cpufreq-plugin the
consumption gets much higher; for instance now, after 1 day, it's
already 17.6. It keeps increasing with time, until I can launch 
no new programs as fork fails, since both ram and swap are filled.
Actually running sid on amd64.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.4
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) (ignored: LC_ALL 
set to [EMAIL PROTECTED])

Versions of packages xfce4-cpufreq-plugin depends on:
ii  libatk1.0-0   1.10.3-1   The ATK accessibility toolkit
ii  libc6 2.3.5-8.1  GNU C Library: Shared libraries an
ii  libcpufreq0   0.3-2  shared library to deal with the cp
ii  libglib2.0-0  2.8.4-2The GLib library of C routines
ii  libgtk2.0-0   2.6.10-2   The GTK+ graphical user interface 
ii  libpango1.0-0 1.8.2-3Layout and rendering of internatio
ii  libxfce4util-14.2.3.2-1  Utility functions library for Xfce
ii  libxfcegui4-3 4.2.3-1Basic GUI C functions for Xfce4
ii  libxml2   2.6.22-2   GNOME XML library
ii  xfce4-panel   4.2.3-1The Xfce4 desktop environment pane
ii  zlib1g1:1.2.3-8  compression library - runtime

xfce4-cpufreq-plugin recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]