forwarded from https://bugzilla.redhat.com/show_bug.cgi?id=610761 Description of problem: I see from htop output sorted by resident memory that the sensor panel on my XFCE desktop is currently taking 412M of RAM, after being logged in for 3 days now. Version-Release number of selected component (if applicable): xfce4-sensors-plugin.x86_64 1.0.0-1.fc12 How reproducible: log into XFCE desktop w/ sensor panel active & watch it for a few days .... Actual results: 412M of RAM after ~3 days .... Expected results: maybe a few hundred KB of RAM .... Additional info: screenshot of HTOP output https://bugzilla.redhat.com/attachment.cgi?id=429037
(In reply to comment #0) > forwarded from https://bugzilla.redhat.com/show_bug.cgi?id=610761 > > Description of problem: I see from htop output sorted by resident memory that > the sensor panel on my XFCE desktop is currently taking 412M of RAM, after > being logged in for 3 days now. > > Version-Release number of selected component (if applicable): > xfce4-sensors-plugin.x86_64 1.0.0-1.fc12 > > How reproducible: log into XFCE desktop w/ sensor panel active & watch it for a > few days .... > > Actual results: 412M of RAM after ~3 days .... > > Expected results: maybe a few hundred KB of RAM .... > > Additional info: screenshot of HTOP output > https://bugzilla.redhat.com/attachment.cgi?id=429037 Can you please indicate how the sensors plugin was built or packaged? I.e., whether libsensors, ACPI or whatever are used. Meanwhile, I experience this on Ubuntu as well but still don't have a clue unless I oversaw some memory allocates that would not be freed. Previously sent patches free'd data from libsensors that is not allowed to be freed.
The package was built with lm_sensors and hddtemp. You can find all files here: http://pkgs.fedoraproject.org/gitweb/?p=xfce4-sensors-plugin.git;a=tree;h=93367abbaea881eedb7ab781cbab8bc4d278df0f;hb=72244ce8acab7aec09cf1ef8e0a4fd8b543845f7 Build log at http://kojipkgs.fedoraproject.org/packages/xfce4-sensors-plugin/1.0.0/1.fc12/data/logs/x86_64/build.log
I still have the impression that libsensors might be to blame due to global variables or the like. Anyway, ongoing problem I am aware of and investigating and monitoring all the time....
I think you aremay be right about libsensors. For me the plugin runs fine for days without increasing memory usage, but I am not using lm_sensors as all my hardware is handled directly through ACPI.
Maybe a clue.. do you use the progress bar (or gtk_cpu which seems to use drawing ? )and a theme that uses gtk-xfce-engine ? If so, that might be bug #8521. To check, try a theme that uses another engine (murrine, aurora...) and see if the leak stops.
(In reply to comment #5) > Maybe a clue.. do you use the progress bar (or gtk_cpu which seems to use > drawing ? )and a theme that uses gtk-xfce-engine ? If so, that might be bug > #8521. To check, try a theme that uses another engine (murrine, aurora...) > and see if the leak stops. So I close that bug report. Landry, thanks for your valuable help and hint.