hello,
it's been couple of weeks since I patched, and there is no memory leak
anymore.^^
I've used several tools to detect problems,
example, valgrind http://valgrind.org/, memwatch(
http://www.linkdata.se/sourcecode/memwatch/)
for python test, i used guppy and it told me there was no leak.
but c
Hi,
In this thread it looks like you may have found a memory leak problem in
collectd python, but I'm not sure. I am seeing a memory leak to in a very
similar situation (though using the following plugin:
https://github.com/mleinart/collectd-haproxy . I'm using the Ubuntu package
collectd-core
Hey,
On Wed, Jan 18, 2012 at 02:22:37AM +0100, Sven Trenkel wrote:
> Oh well, I uploaded a patch to github, it should appear in the
> official collectd repository soonish.
thanks for fixing this, Sven! I've cherry-picked the commit to the
collectd-4.10 branch which is available from git.verplant.
As always in life the solution was not as simple as it appeared to be.
Oh well, I uploaded a patch to github, it should appear in the official
collectd repository soonish.
If you want to compile a it yourself from source, this patch should work
on the collectd-5.0 branch:
http://www.semidefinit
I am using version 5.0.1 compiled with the spec file included in the
sources. I have a single patch applied for summarizing CPU stats, but
that's about it. I'm eager to check out your patch. Thanks for
looking into this!
___
collectd mailing list
coll
I am using version 5.0.1 compiled with the spec file included in the
sources. I have a single patch applied for summarizing CPU stats, but
that's about it. I'm eager to check out your patch. Thanks for
looking into this!
___
collectd mailing list
coll
Never mind, I think I found the bug. I'll test it tomorrow. If you
compiled collectd yourself I'll send you a patch if you tell me the
exact version number you're using.
___
collectd mailing list
collectd@verplant.org
http://mailman.verplant.org/listi
What version of collectd are you using?
And until we find the cause of this behavior you might try to pull the
constant parts of the submitted value out of the for loop. So,
v = collectd.Values()
v.plugin = 'mongostats'
v.type = 'counter'
could be put before the loop as it's just creating and
I wrote a simple python reader plugin to collect a few stats from my
local mongo server. I noticed that over time, my process would
continually grow until it consumed >100MB of memory. If I simply
comment out my 'v.dispatch()' function, the memory leak goes away. Is
this an issue with collectd,