Memory leak in sensors panel plugin

[Fabian Nowak]

Weedy,

in the past, other people have also experienced memory usage grow.
However, they found out that it was due to the selected Gtk theme they
had, at least they said so.

There have also been bugreports in bugzilla and further investigations,
no further issues could be found so far. Though, another reason might be
running a very old version of the plugin.

Finally, with an update interval of only 1 second, issues might also
arise, as already indicated, by the used libraries and maybe drivers.

So, please, we need a regular bugzilla entry with OS, sensors plugin
version, your hardware as well, the sensors chosen, and some more help
in investigating. 

Not everyone has coretemp, it comes from lmsensors device
"coretemp-isa-0000", e.g., with "Core 0" then. And lmsensors uses
libsensors.

Hope that clarifies, 

Fabian


Am Mittwoch, den 26.08.2015, 15:51 +0200 schrieb Olivier Fourdan:
> On 26 August 2015 at 15:35, houghi <houghi at houghi.org> wrote:
> 
>         On 2015-08-26 14:43, Weedy wrote:
>                 I use coretemp, i8k, and nvidia sensors.
>                 
>                 For the test I nuked the sensors plugin and added it
>                 back with only
>                 "core 0" from the coretemp-0 sensor.
>                 One second refresh. It always starts up around 50mb
>                 RSS, and I end up
>                 killing it around 85+.
>                 
>                 After running this a few times I think the leak is the
>                 the general
>                 result fetching code.
>         
>         It could well be the coretemp-0 pushing code on your machine. 
>         ​[...]
> 
> 
> ​I don't understand that sentence.
> ​
>  
>         
>         
>                 While I didn't specifically try fans only next,
>                 everyone should have coretemp. And if everyone has
>                 coretemp then
>                 anyone else should be able to corroborate this.
>         
>         And that is not the case, so your conclusion is in error.
> 
> 
> ​
> Best way to investigate suspected memory leaks is to use valgrind.
> 
> 
> Cheers,
> Olivier